Automatic rebuild of R derived packages on every new major version.
by José Abílio Matos
Hi,
A new version of R is approaching, R 2.4.0 is scheduled for the first days of
October.
When version 2.4 is recompiled we need to recompile all the packages that
depend on R.
rpy needs to be compile for every new 2.4.x release, but R packages only need
to be release for each x.y.0 release.
That is exactly what happens with python, every package needs to be rebuild
because pyc files depend on a major version.
Python does not present any major problem since the core of the language is
in Core, and every new version only appears once in the Core release and only
minor updates are allowed during the distribution life time.
R core language is in Extras and the correct way to build a new version is
to rebuild the core language and then the different packages according to its
dependencies.
This procedure is tedious and error prone, especially as more and more
packages enter Extras. Would it be possible to automate to some extent this
procedure.
I guess that this procedure could be of interest for other languages that
don't go in Core.
Should I bring this issue to Extras or Packagers mailing list, since this
problem seems general enough and not only limited to R.
What do other think?
--
José Abílio
17 years, 2 months
- 1
- 0
rebuild for fc6
by José Abílio Matos
Hi Spot,
to you have any estimated time to rebuild R for FC6?
I am holding the update of my packages related with R to after your update.
rpy
R-mAr
R-waveslim
R-wavethresh
Although the reason is probably a bit silly, since I am not sure how
the .so's of those packages (those where it applies) depends on how R is
compiled. The reason for the mass recompile is related with the linker, so I
decided to play safe.
Better to be sorrow than to be sorry. :-)
--
José Abílio
17 years, 2 months
- 2
- 2
- ← Newer
- 1
- Older →