From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] FEATURES use or misuse?
Date: Tue, 3 Nov 2009 20:58:27 +0000 [thread overview]
Message-ID: <20091103205827.339c1613@snowcone> (raw)
In-Reply-To: <200911032136.18242.patrick@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
On Tue, 3 Nov 2009 21:36:18 +0100
Patrick Lauer <patrick@gentoo.org> wrote:
> Userpriv I've seen the funny idea to check if UID=0 and such.
Yes, and that 'funny idea' has the added advantage of working even if
userpriv is in FEATURES but not actually enabled (yes, that can happen).
> > > To quote:
> > > "FEATURES is a portage specific package manager configuration
> > > variable not specified in PMS and cannot reliably be used in
> > > ebuilds or eclasses."
> >
> > Makes sense to me atm.
>
> Makes no sense to me, but then I seem to be special :)
PMS doesn't document user configuration. If PMS did document user
configuration, it would mean that user configuration file formats
couldn't arbitrarily be changed between package manager versions as
they are now.
If FEATURES were specified by PMS, Portage wouldn't be able to change
the meaning of its entries without careful EAPI controls. So far as I'm
aware, no-one is in favour of introducing such a restriction. There
are easy alternatives available, and unlike checking FEATURES, those
alternatives actually work.
> And all my attempts to get it fixed have been deflected, so I'll keep
> ridiculing it until it stops being a failwhale.
Patrick, perhaps you would find your efforts more fruitful were you to
respond to reviews of your patches by fixing the issues raised, instead
of using every available opportunity you can find to take pot-shots at
PMS, close off legitimate bugs as INVALID and generally attempt to make
life as hard as possible for those for whom PMS matters most.
Of the small number of patches that have ended up being rejected from
PMS, all but one have been yours, and the one that wasn't was because
the author had mistranslated a phrase. I'd appreciate it if you would
stop to consider why this is the case.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-03 20:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 15:48 [gentoo-dev] FEATURES use or misuse? Patrick Lauer
2009-11-03 17:27 ` Sebastian Pipping
2009-11-03 20:36 ` Patrick Lauer
2009-11-03 20:58 ` Ciaran McCreesh [this message]
2009-11-03 22:28 ` Patrick Lauer
2009-11-04 0:11 ` [gentoo-dev] " Ryan Hill
2009-11-04 8:26 ` Patrick Lauer
2009-11-05 1:36 ` Ryan Hill
2009-11-05 4:56 ` [gentoo-dev] a pragmatic approach to FEATURES [was FEATURES use or misuse?] Brian Harring
2009-11-05 8:49 ` Thilo Bangert
2009-11-05 9:36 ` Brian Harring
2009-11-08 9:21 ` Thilo Bangert
2009-11-03 21:26 ` [gentoo-dev] FEATURES use or misuse? Alexis Ballier
2009-11-03 22:04 ` Patrick Lauer
2009-11-03 22:26 ` Ciaran McCreesh
2009-11-04 0:33 ` Sebastian Pipping
2009-11-04 8:26 ` Patrick Lauer
2009-11-03 23:04 ` David Leverton
2009-11-04 1:31 ` [gentoo-dev] " Duncan
2009-11-04 22:12 ` Peter Hjalmarsson
2009-11-05 5:04 ` Brian Harring
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=20091103205827.339c1613@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--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