[codeface] Re: mailing list analysis
- From: Wolfgang Mauerer <wm@xxxxxxxxxxxxxxxx>
- To: codeface@xxxxxxxxxxxxx
- Date: Sun, 27 Jul 2014 01:07:59 +0200
Dear all,
Am 26/07/2014 22:24, schrieb Roger Meier:
Quoting Mitchell Joblin <joblin.m@xxxxxxxxx>:
The latest version of the 'tm' package (v0.6) breaks the mailing list
analysis when the 'snatm' package calls the function tm::Source(..). The
current solution is to use an older version of the tm package. Version
0.5.10 of the tm package does not experience this problem.
.Rprofile and packages.R might support version selection options to avoid
such situations.
IIRC, we do also have some checks in the ML analysis code to ensure
appropriate versions for some packages. However, such an approach
usually works to check for minimal version requirements; the reverse
direction should always be feasible assuming the upstream is
backwards compatible. If not, changes are required anyway, so
excluding too-recent versions will be a temporary fix by design.
We should of course notify the maintainers of the 'snatm' package so that
this gets fixed in a future release. Perhaps we also need another
strategy
to prevent this type of problem from occurring again.
I'd prefer to fix the upstream packages. Since I do have commit rights
for snatm, it should not be difficult to convince the maintainer we need
the patch :) Do you happen to have one, or should I look into the issue?
Actually, it seems to me we're the only real users of snatm anyway.
Maybe we should merge the complete codebase into codeface to avoid
the extra complications any API changes in dependencies bring in
the future. Opinions on that? Would not be a license problem, and
there has been no snatm activity during the last two years except
for our contributions.
We could install specific versions of R packages that we know to work
rather than assuming the latest versions will always function properly
together. At the very least, we should publish versions of the packages
that we know to work correctly. For first time installers of Codeface
these
incompatible package issues are difficult to identify, and will probably
cause the user to just abandon the project.
Using the Vagrantfile and probably adding a .travis.yml is another option
to improve usability and to run unit tests on master branch and pull
requests.
that would be very desirable indeed. Trouble is that codeface is
currently a bit ...understaffed, but that may change sooner or later.
Thanks & best regards, Wolfgang
all the best!
-roger
Cheers,
Mitchell Joblin
Other related posts:
