| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Simon Stelling wrote: |
| 5 |
> Having them in an eclass raises the problem of ebuilds having to inherit |
| 6 |
> said eclass, though. Even if it would be the correct way, I am not all |
| 7 |
> that keen on adding a 'inherit install-helpers' to ~15'000 ebuilds |
| 8 |
|
| 9 |
For awhile I've been wanting something like a repo-level profile that everything |
| 10 |
in the tree implicitly inherits from. We have ${PORTDIR}/profiles/base/, which |
| 11 |
is similar, |
| 12 |
but that has to be explicitly inherited by the user-level profile in order to |
| 13 |
have any relevance. |
| 14 |
|
| 15 |
If we implement the repo-level profile, it can have a |
| 16 |
bashrc (much like profile.bashrc) that acts as a repo-level ebuild template |
| 17 |
(like install-helpers.eclass). Actually, the repo-level profile already exists |
| 18 |
in the form of files such as ${PORTDIR}/profiles/{package.mask,arch.list}, |
| 19 |
though it doesn't yet have support for a bashrc (ebuild template). |
| 20 |
|
| 21 |
Zac |
| 22 |
-----BEGIN PGP SIGNATURE----- |
| 23 |
Version: GnuPG v1.4.5 (GNU/Linux) |
| 24 |
|
| 25 |
iD8DBQFE/dUQ/ejvha5XGaMRArnsAJ4wUqhCn1xFEbrbc5AMkviQEQNx+gCfZkYa |
| 26 |
mQilAJT7wvO96WSQFOZ5IJ8= |
| 27 |
=Pjrs |
| 28 |
-----END PGP SIGNATURE----- |
| 29 |
-- |
| 30 |
gentoo-portage-dev@g.o mailing list |
Archives