Grant posted on Fri, 25 May 2012 23:01:42 -0700 as excerpted: >>> May I ask why you force the g-cpan category to dev-perl? >> >> Using that category solves many issues in advance, ie: if you generated >> an ebuild locally, and then we provided a maintained copy, >> portage would just switch from one to the other seamlessly where needed >> without you having to modify all ebuilds that depend on it.
> I was thinking it would be nice to know which ebuilds came from g-cpan, > but now that I think about it I suppose it doesn't really matter. Not a perl-head, but if I've been following the thread correctly... If you manage the overlays correctly (see the earlier note about it using the last one in the list), you'll know based on what overlay the ebuild is from. Simply create an overlay specifically for g-cpan and make it last in the list. Simple enough, assuming I'm not horribly mixed up, anyway. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
