From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Proposal of accepting arguments to `default` in src_install (and more?) phases in EAPI=5 (for the next council meeting?)
Date: Mon, 14 May 2012 04:58:30 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.05.14.04.58.29@cox.net> (raw)
In-Reply-To: 20398.44617.452031.712699@a1i15.kph.uni-mainz.de
Ulrich Mueller posted on Sat, 12 May 2012 20:39:05 +0200 as excerpted:
> On Sat, 12 May 2012, Michał Górny wrote:
>
>> EXTRA_EMAKE isn't supposed to be mentioned there. It's an internal use
>> variable for users who need to pass something specific to make.
>
> You are right, of course.
> I guess the following ebuilds should be fixed then:
>
> eclass/bsdmk.eclass
> eclass/python.eclass
> eclass/scons-utils.eclass
> dev-db/redis/redis-2.2.12.ebuild
> dev-db/redis/redis-2.4.4-r1.ebuild
> dev-db/redis/redis-2.4.7.ebuild
> dev-db/redis/redis-2.4.8.ebuild
> dev-db/redis/redis-2.4.10.ebuild
> dev-db/redis/redis-2.4.13.ebuild
> gnome-base/gconf/gconf-2.32.4.ebuild
> net-misc/mico/mico-2.3.13-r5.ebuild
> sci-chemistry/ccp4-apps/ccp4-apps-6.1.3-r10.ebuild
> sys-fs/udev/udev-171-r5.ebuild
Ouch, in eclasses too! Yes. If I came across that I'd have filed bugs
immediately, as I actually use EXTRA_* occasionally as a user, myself!
Of course there's also the other PM users who would find these bugs.
Is someone else filing bugs, or should I? Probably a tracker, along with
individual bugs (only one for redis, tho)?
What about a repoman check? Bug for that too?
(If the answer is me do it, please bump me in say 10 days or so if I
don't. I'm having stability problems on my main machine right now. ATA
resets and I've already switched sata card and hard drive. Probably time
for a new mobo/cpus/etc, but no $$ for it. =:^( I may end up netbook-
only, severely restricting gentoo upgrades for awhile!)
--
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
next prev parent reply other threads:[~2012-05-14 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 16:50 [gentoo-dev] Proposal of accepting arguments to `default` in src_install (and more?) phases in EAPI=5 (for the next council meeting?) Samuli Suominen
2012-05-12 17:57 ` Ulrich Mueller
2012-05-12 18:09 ` Michał Górny
2012-05-12 18:12 ` Samuli Suominen
2012-05-12 18:39 ` Ulrich Mueller
2012-05-14 4:58 ` Duncan [this message]
2012-05-14 14:05 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
2012-05-12 18:42 ` [gentoo-dev] " julian
2012-05-12 18:43 ` hasufell
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.2012.05.14.04.58.29@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