Tomáš Chvátal <scarabeus@g.o> wrote:
> On Sunday 30 November 2008 14:23:48 Diego 'Flameeyes' Pettenò wrote:
> > I have a very quick proposal: why don't we move the packages' homepage
> > in metadata.xml (since it's usually unique for all the versions) and we
> > get rid of the variable for the next EAPI version?
> I would rather see something like:
> 
> packagename/metadata.xml
> packagename/package-base.ebuild
> packagename/packagename-version.ebuild
> packagename/Manifest
> packagename/Changelog

Correct me if i'm wrong, but this doesn't address the problem with
multiple versions having multiple homepages.
I'm with Diego here that this should be *very* rare.

Can somebody verify this? I mean just throw a little shell script on the
portage tree showing which ebuilds differ in HOMEPAGE but still have the
same path.. my poor ibook would take too long for such a thing, so
sorry, no data here.

And while your proposal sounds more compliant to the DRY principle, i
would object it on the basis that it makes a single ebuild actually
harder to understand as you have to read (1) eclasses, (2) -base.ebuild
and (3) -version.ebuild.
-- 
Regards, Matti Bickel
Signed/Encrypted email preferred (key 4849EC6C)