From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GLEP 55: another approach: display pretty messages with old PMs
Date: Fri, 29 May 2009 16:09:24 +0000 (UTC) [thread overview]
Message-ID: <pan.2009.05.29.16.09.24@cox.net> (raw)
In-Reply-To: 1243610264.27150.293.camel@sapc154.salomon.at
Michael Haubenwallner <haubi@gentoo.org> posted
1243610264.27150.293.camel@sapc154.salomon.at, excerpted below, on Fri,
29 May 2009 17:17:44 +0200:
> Wouldn't it be possible to avoid both the extension change and another
> extended wait period for new incompatible(*) EAPIs, when we do this
> early and silent exit hack for unsupported ebuilds with old PMs that
> still do full interpretation for EAPI detection?
Possibly. I forgot about the context (the inherit eapi.eclass hack) when
I wrote the previous (until /after/ I posted, naturally, probably when
you noticed that 4.ebuild thing too, of course =:^).
But the possibility had been proposed before and I don't remember what
came of it, nor have I been following close enough to know if there's
another caveat somewhere that shoots down the eapi.eclass hack, or not.
I'm sure someone else will supply the reason it didn't go anywhere.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2009-05-29 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 17:17 [gentoo-dev] GLEP 55: another approach: display pretty messages with old PMs Michael Haubenwallner
2009-05-29 8:14 ` [gentoo-dev] " Michael Haubenwallner
2009-05-29 10:42 ` Duncan
2009-05-29 15:17 ` Michael Haubenwallner
2009-05-29 16:09 ` Duncan [this message]
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=pan.2009.05.29.16.09.24@cox.net \
--to=1i5t5.duncan@cox.net \
--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