From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: hardened glibc and gcc dependencies
Date: Sun, 30 Oct 2011 19:04:32 -0600 [thread overview]
Message-ID: <20111030190432.570c5a11@gentoo.org> (raw)
In-Reply-To: 4EADCE8C.6010501@gentoo.org
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Mon, 31 Oct 2011 00:24:12 +0200
Petteri Räty <betelgeuse@gentoo.org> wrote:
> On 28.10.2011 2.50, Mike Frysinger wrote:
> > On Fri, Oct 28, 2011 at 01:47, Ryan Hill wrote:
> >> On Thu, 27 Oct 2011 23:03:12 +0530 Nirbheek Chauhan wrote:
> >>> So, I honestly see no reason why toolchain should not start using EAPI 2.
> >>
> >> I await your patch to toolchain.eclass. :P
> >
> > i wouldn't bother as it's most likely not going to be accepted at this time
> >
>
> Why not? EAPI 2 was approved more than 3 years ago. I don't think
> there's a problem policy wise making all ebuilds able to use it these days.
Porting toolchain.eclass to another EAPI would require sacrificing more
chickens than urban zoning regulations permit. I'm working on finding a small
rural acreage close to a local ley line. Will keep you posted.
Or you could use ewarns and dies like they were for years before USE deps got
implemented.
--
fonts, gcc-porting, it makes no sense how it makes no sense
toolchain, wxwidgets but i'll take it free anytime
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-31 0:55 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 ` [gentoo-dev] " Nirbheek Chauhan
2011-10-27 23:47 ` [gentoo-dev] " 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 [this message]
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=20111030190432.570c5a11@gentoo.org \
--to=dirtyepic@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