>>>>> "DB" == Donnie Berkholz <email@example.com> writes:
JC> I find that g-cran and portage master branches are incompatible.
DB> Ever do anything with this? Just tried g-cran myself and I'm hitting
DB> it too, on portage 2.2.
No, I just spent some time thinking about the problem.
I hat to sound to critical, given that it was written as a gsoc project,
but the lack of real Manifest files made g-cran highly unreliable, even
when it worked at all. A common problem I had was failed downloads, due
to network issues. Unlike with other packages, after such a file one
has to manually remove the g-cran downloads before portage can download
a working copy. And you can't use ebuild(1) to debug build issues with
c-cran ebuilds; only emerge(1) ever worked.
There were also some dependency bugs. Both unnecessary and
unfulfillable deps, and also some missing deps. I doubt that the
latter can be reliably fixed, but the former can be filtered out.
Given that osuosl is a cran mirror, I think a better solution would be
an overlay published on git.overlays.gentoo.org, updated daily after
the mirror updates. With local access to the src files, the script
can generate proper Manifest files.
The SRC_URIs should point at the (IIRC) archive locations rather than
at the src/crontib locations, to ensure that out-of-date overlays still
work. And it should have ebuilds for two or three versions, just in
case there are any issues.
Such an overlay would alleviate most of the issues, and if done at a
site (such as osuosl) which is already a cran mirror, would not require
excessive network bandwidth.
I'd be happy to spend some time a script to build such an overlay, and
can do some limited testing of it, but do not have the net bw to run
such a script in production, or to fully test it.
James Cloos <cloos@...> OpenPGP: 1024D/ED7DAEA6