>> 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. > > ie: > > if a package was installed in perl-gcpan/ instead ( which used to be > the case iirc ), you then have: > > perl-gcpan/foo : DEPENDS dev-perl/bar > perl-gcpan/baz : DEPENDS perl-gcpan/foo > > And if you want to cede development of "foo" to an overlay/gentoo, > you'd have to change perl-gcpan/baz to point to perl-gcpan/foo > instead. > > With the packages all in dev-perl, no such changes are required.
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. Thanks a lot for your help! - Grant
