| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Tomáš Chvátal yazmış: |
| 5 |
> On Sunday 30 November 2008 14:23:48 Diego 'Flameeyes' Pettenò wrote: |
| 6 |
>> I have a very quick proposal: why don't we move the packages' homepage |
| 7 |
>> in metadata.xml (since it's usually unique for all the versions) and we |
| 8 |
>> get rid of the variable for the next EAPI version? |
| 9 |
> I would rather see something like: |
| 10 |
> |
| 11 |
> packagename/metadata.xml |
| 12 |
> packagename/package-base.ebuild |
| 13 |
I've been thinking of something like this for a long time. It would |
| 14 |
greatly improve maintanance (we could put some common ebuild logic |
| 15 |
there,too) and reduce the tree size. |
| 16 |
> packagename/packagename-version.ebuild |
| 17 |
> packagename/Manifest |
| 18 |
> packagename/Changelog |
| 19 |
> |
| 20 |
> Where package-base would store everything basic for the ebuild, licences and |
| 21 |
> so on, and in package-version would be only specific changes for the version |
| 22 |
> (for example patching Makefile). |
| 23 |
> |
| 24 |
> Variables will be overridable this way and thus i think it would be nicer. |
| 25 |
> |
| 26 |
|
| 27 |
- -- |
| 28 |
Sincerely, |
| 29 |
Serkan KABA |
| 30 |
Gentoo/Java |
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 33 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 34 |
|
| 35 |
iEYEARECAAYFAkkymmIACgkQRh6X64ivZaKaNQCfYT0Db8zjcIYkzZcPPn83IxMM |
| 36 |
UIgAniA8kdc511KJ9eaDNwp8YR7CqKkf |
| 37 |
=JcT+ |
| 38 |
-----END PGP SIGNATURE----- |
Archives