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