From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] What are eblits?
Date: Sun, 29 May 2016 10:25:58 +0200 [thread overview]
Message-ID: <22346.42902.412224.358607@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <CAGfcS_mW_u43aAvaqRn4fU6xH+rZq7pkT6e8Vc9OGod0uCjr0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
>>>>> On Sun, 29 May 2016, Rich Freeman wrote:
> What I would love to see is this be standardized. An eclass or a
> GLEP seems like the logical approach.
I am strongly opposed against this. Ebuilds should not source
executable code from random locations. This is also a huge QA
violation, since PMS neither guarantees FILESDIR to be available in
global scope (so especially, not during metadata generation), nor in
any of the pkg_* phases (like pkg_setup, where mips-sources sources
its eblits).
If there really is a need for such a feature, we should rather follow
an approach like the per-package eclasses previously suggested by mabi
and antarus [1], and support a pkg-inherit function in the next EAPI.
(Though I wouldn't add a new function, but add an option to inherit,
like "inherit -p".)
We could even think about per-category eclasses ("inherit -c"),
although it is not obvious where one would store them.
Ulrich
[1] https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/users/antarus/projects/gleps/glep-XX.txt?view=markup
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2016-05-29 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 22:28 [gentoo-dev] What are eblits? rindeal
2016-05-27 1:28 ` Kent Fredric
2016-05-27 14:26 ` konsolebox
2016-05-29 1:11 ` Joshua Kinard
2016-05-29 6:02 ` Rich Freeman
2016-05-29 8:25 ` Ulrich Mueller [this message]
2016-05-29 12:29 ` Rich Freeman
2016-05-29 14:20 ` Joshua Kinard
2016-05-27 1:56 ` [gentoo-dev] " Duncan
2016-05-27 13:06 ` [gentoo-dev] " Ciaran McCreesh
2016-05-27 17:35 ` [gentoo-dev] " rindeal
2016-05-28 5:07 ` Kent Fredric
2016-05-28 18:40 ` Duncan
2016-05-29 1:05 ` [gentoo-dev] " Joshua Kinard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22346.42902.412224.358607@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox