From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] hardened glibc and gcc dependencies
Date: Thu, 27 Oct 2011 23:03:12 +0530 [thread overview]
Message-ID: <CADqQcK4Up37WSOGBgsG-Mn53pLS-RM8jZRA_h9XujQB7YZ6SGw@mail.gmail.com> (raw)
In-Reply-To: <4EA98204.4030601@gentoo.org>
On Thu, Oct 27, 2011 at 9:38 PM, "Paweł Hajdan, Jr."
<phajdan.jr@gentoo.org> wrote:
> On 10/27/11 11:03 AM, "Paweł Hajdan, Jr." wrote:
>> In glibc: DEPEND="gcc[hardened?]"
>> In gcc: PDEPEND="elibc_glibc? glibc[hardened?]"
>
> I even got an OK on #gentoo-hardened, but I just realized that EAPI-0
> (that both packages in question use) doesn't allow use deps like
> [hardened?].
>
> I guess bumping the EAPI on those packages is not an option (is it?), so
> I'm going to do some more experiments to see if there are more possible
> problems.
>
As per council approval in the last meeting, profiles/ is now EAPI 1.
EAPI 2 usage in profiles was not a blocker due to portage version
problems, but due to unresolved questions about cat/pkg[use] atoms in
package.mask etc. Barring those, EAPI 2 would've been approved for
profiles/ as well.
So, I honestly see no reason why toolchain should not start using EAPI 2.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
next prev parent reply other threads:[~2011-10-27 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 9:03 [gentoo-dev] hardened glibc and gcc dependencies "Paweł Hajdan, Jr."
2011-10-27 16:08 ` "Paweł Hajdan, Jr."
2011-10-27 16:49 ` [gentoo-dev] " Duncan
2011-10-27 17:33 ` Nirbheek Chauhan [this message]
2011-10-27 23:47 ` Ryan Hill
2011-10-27 23:50 ` Mike Frysinger
2011-10-28 11:36 ` Anthony G. Basile
2011-10-28 17:20 ` Nirbheek Chauhan
2011-10-30 22:24 ` Petteri Räty
2011-10-31 1:04 ` Ryan Hill
2011-10-28 3:03 ` Nirbheek Chauhan
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=CADqQcK4Up37WSOGBgsG-Mn53pLS-RM8jZRA_h9XujQB7YZ6SGw@mail.gmail.com \
--to=nirbheek@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