-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Volkov yazmış: > В Вск, 30/11/2008 в 14:50 +0100, Tobias Scherbaum пишет: >> In most (nearly all?) cases a HOMEPAGE change does also affect older >> versions. >> Does someone have an example where older versions stay at an old homepage >> and newer versions moved to a new homepage? > > Yes. This is quite a common case when one upstream stopped development > of the package and new developer took it. traceroute, flow-tools are > just examples from the top of my head. I remember I saw more such > things... > > Also sometimes it's useful to have different HOMEPAGE for different > versions. > > > And in general, Diego. What are you trying to improve with this change? > The original intention was to separate common information from all > ebuilds into metadata.xml. But obviously, HOMEPAGE changes from ebuild > to ebuild. Now if intention is separate some information from ebuild > into metadata.xml then, please, tell me what is the criterion for such > information? Why not LICENSE? Currently I don't think this change worth > our efforts... > LICENSE should definetely be avoided to be defined per-package. Upstream may decide to relicense new version of packages. - -- Sincerely, Serkan KABA Gentoo/Java -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkkyrJ0ACgkQRh6X64ivZaI4EwCfWECIM3Hecu04yHCeoCKEJqki VMQAnj+aIeQ5Bf9cA0iQm/wT8U7hZWAV =wW6Q -----END PGP SIGNATURE-----
