From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] EAPI6 Features
Date: Sun, 08 Jun 2014 21:15:18 +0200 [thread overview]
Message-ID: <1402254918.3631.4.camel@belkin5> (raw)
In-Reply-To: <21396.30067.503349.626165@a1i15.kph.uni-mainz.de>
El dom, 08-06-2014 a las 16:38 +0200, Ulrich Mueller escribió:
[...]
> >> d) Source eclasses only once
> >> Bug #422533
>
> > Does anybody still want this included? It seems to me like the list
> > discussion was leading in a different direction, but it isn't 100%
> > clear to me if this is the case.
>
> Right, discussion has died down. Many eclasses now use a mechanism
> equivalent to the one in C header files, which seems to do the job.
>
Last time I checked, there were still some eclasses not doing that
(either the "spank" way or the way from python -r1 eclasses). Not sure
if this was intended and why that eclasses are pending :/ If there is no
technical issue in fixing them (probably with the way used in python
eclasses ;)), why not simply go ahead and fix them? (not sure how could
we check for this issue in future eclasses that could be added without
this tricks included)
next prev parent reply other threads:[~2014-06-08 19:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 13:04 [gentoo-project] EAPI6 Features Rich Freeman
2014-06-08 14:38 ` Ulrich Mueller
2014-06-08 15:09 ` Rich Freeman
2014-06-08 19:15 ` Pacho Ramos [this message]
2014-06-08 20:56 ` Ulrich Mueller
2014-06-09 8:50 ` Pacho Ramos
2014-06-08 21:49 ` Michał Górny
2014-06-08 15:29 ` Jeroen Roovers
2014-06-08 16:56 ` Ulrich Mueller
2014-06-08 17:22 ` Andreas K. Huettel
2014-06-08 17:26 ` Ciaran McCreesh
2014-06-08 17:28 ` Ulrich Mueller
2014-06-08 21:40 ` Michał Górny
2014-06-08 22:58 ` Rich Freeman
2014-06-09 2:57 ` Michał Górny
2014-06-09 10:12 ` Ulrich Mueller
2014-06-09 14:31 ` Ian Stakenvicius
2014-06-09 15:29 ` [gentoo-project] " Jonathan Callen
2014-06-09 16:23 ` Ulrich Mueller
2014-06-09 16:31 ` Michał Górny
2014-06-09 16:43 ` Ian Stakenvicius
2014-06-09 16:47 ` Ulrich Mueller
2014-06-09 19:20 ` Jeroen Roovers
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=1402254918.3631.4.camel@belkin5 \
--to=pacho@gentoo.org \
--cc=gentoo-project@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