From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] Planning for the transition to EAPI="1" support
Date: Thu, 4 Oct 2007 23:34:14 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.10.04.23.34.13@cox.net> (raw)
In-Reply-To: 4705654D.7090102@gentoo.org
Zac Medico <zmedico@gentoo.org> posted 4705654D.7090102@gentoo.org,
excerpted below, on Thu, 04 Oct 2007 15:12:29 -0700:
> Due to popular demand, I'm preparing a sys-apps/portage-2.1.3.12 release
> that will have support for EAPI="1". The extensions planned for
> inclusion are SLOT dependencies (#174405), IUSE defaults (#174410), and
> ECONF_SOURCE support for the default src_compile function (#179380).
What about news? It has been implemented but ran into a bug (portage
hadn't fully implemented the news reader, IIRC) the first time someone
tried to actually deploy it. Is that too controversial or has portage
still no full implementation?
I'm sure you've not forgotten about it and not pressin' if it's not
ready, as I agree with the "release early, release often" idea, just
askin', as I've not seen anything on it in awhile and as a user, the
feature would be nice to have. =8^)
Or is it part of API-0 now, and implemented, just not yet used?
--
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
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-04 23:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 22:12 [gentoo-dev] [RFC] Planning for the transition to EAPI="1" support Zac Medico
2007-10-04 22:23 ` Arfrever Frehtes Taifersar Arahesis
2007-10-04 22:32 ` Dan
2007-10-04 23:34 ` Duncan [this message]
2007-10-05 0:30 ` [gentoo-dev] " Petteri Räty
2007-10-05 2:26 ` Marius Mauch
2007-10-05 8:39 ` Duncan
2007-10-05 10:01 ` Bo Ørsted Andresen
2007-10-05 12:34 ` Marius Mauch
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.2007.10.04.23.34.13@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