Hello, thanks for the reply.
On the positive side there's no reason why a source-only ebuild couldn't
be added back to this overlay. I've still got the previous working
version so that's available as a starting point if it would help anyone.
The problem is the same as it's always been, though, that the Perl
module versions in Gentoo have moved on (in some cases quite
considerably) from those that LMS was designed to work with. This makes
it quite difficult to find all the problems and introduce patches to the
CPAN modules and/or LMS in order to get them to work together. This
might have been practical with a handful of dependencies but from memory
I think I had to wrangle about 70-80 CPAN module dependencies the last
time. That really wasn't a fun experience and I was never very convinced
there weren't problems introduced due to differences in the dependency
versions that I couldn't get to the bottom of.
One way around it might be to include older CPAN modules in the overlay
but this is really no better than keeping the 'bundled' modules with the
server -- it would provoke the same arguments that old CPAN dependencies
might be somehow 'insecure'.
I don't think the 'bundled' version of the ebuild is any less likely to
be supportable than an unbundled one going forward, and it's certainly
lower effort for the maintainer. Although the ebuild is called '...-bin'
it's not really binary and all the Perl source is in there to be patched
as necessary. I'm rather hoping to get it working with Perl 5.16 at some
point when I have some time to try as that's the major reason why it
might not be runnable in the near-term, and I can include those patches
in the -bin ebuild just as easily.
Stuart
On 12/19/2012 03:44 PM, Havin_it wrote:
> Stuart, thanks for posting this, I'm an infrequent updater so goodness
> knows when I would have learned of this otherwise.
>
> Little sad to see this move happen (it sorta feels like a stripping away
> of some of the package's "legitimacy" in the Gentoo ecosystem, much
> though I tell myself this is not really accurate) but I know it is for
> good reasons and it has obviously been a hell of a package to curate
> in-tree (I've seen many of the bugs).
>
> Just a small question: does the move to an overlay improve the scope for
> reanimating the old ("unbundled") source ebuild? I do remember that
> many of the old bugs seemed to trace back to incompatibilities between
> the bundled modules and the in-tree versions, so I guess that kind of
> issue has not gone away and I dare say this is not an avenue you
> personally care to go down again, but if others were to attempt this,
> (a) would a source ebuild be welcome in this overlay and (b) would you
> have any advice on the subject?
>
> I'm not throwing my hat in the ring (no speaky Perl) but if/when LMS
> eventually gets totally orphaned, it would be good if a project were
> already well underway to keep the codebase buildable against newer
> systems. What do you think?
>
>
> ------------------------------------------------------------------------
> Havin_it's Profile: http://forums.slimdevices.com/member.php?userid=12661
> View this thread: http://forums.slimdevices.com/showthread.php?t=97562
>
> _______________________________________________
> unix mailing list
> [email protected]
> http://lists.slimdevices.com/mailman/listinfo/unix
>
--
Stuart Hickinbottom
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
