| 1 |
El dom, 30-11-2008 a las 14:23 +0100, Diego 'Flameeyes' Pettenò |
| 2 |
escribió: |
| 3 |
> I have a very quick proposal: why don't we move the packages' homepage |
| 4 |
> in metadata.xml (since it's usually unique for all the versions) and we |
| 5 |
> get rid of the variable for the next EAPI version? |
| 6 |
> |
| 7 |
|
| 8 |
> |
| 9 |
> Please submit all comments, as long as they are not "I don't like XML" |
| 10 |
> or "XML is the wrong answer" and similar since the point here is not to |
| 11 |
> discuss the format of metadata but rather where to have it. |
| 12 |
|
| 13 |
As suggested by Ciaran and Serkan, this could also be achieved with |
| 14 |
per-package eclasses [1]. |
| 15 |
|
| 16 |
That way, it would be easy to avoid duplication of not only HOMEPAGE but |
| 17 |
also SRC_URI, LICENSE, or any other part of an ebuild. |
| 18 |
|
| 19 |
In fact, this idea is already being used in the tree in the form of bash |
| 20 |
scripts in ${FILESDIR} that are source'd in the ebuild [2]. |
| 21 |
|
| 22 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=69714 |
| 23 |
[2] |
| 24 |
http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-libs/glibc/files/eblits/ |
| 25 |
|
| 26 |
Regards, |
| 27 |
-- |
| 28 |
Santiago Moisés Mola |
| 29 |
Jabber: cooldwind@×××××.com | GPG: AAD203B5 |
Archives