public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: FEATURES use or misuse?
Date: Wed, 4 Nov 2009 09:26:10 +0100	[thread overview]
Message-ID: <200911040926.11069.patrick@gentoo.org> (raw)
In-Reply-To: <20091103181139.70a13d6b@gentoo.org>

On Wednesday 04 November 2009 01:11:39 Ryan Hill wrote:
> On Tue, 3 Nov 2009 23:28:57 +0100
> 
> Patrick Lauer <patrick@gentoo.org> wrote:
> > And then why bother when the tree doesn't reflect PMS.
> 
> Maybe if some people would stop ignoring PMS on whim because they don't
>  agree with something in it this wouldn't be the case.

Well, we have at least one prior discussion and a year of precedent on the 
bash 3.0 / 3.2 thing. Since there were no sanctions for doing it, there's no 
way to break things with it (because you have a recent enough bash guaranteed) 
and it is very convenient people started using it.

After a year of use (and getting used more and more) I just don't see how any 
sane person can think about forbidding it NOW. It's too late. We've moved on. 
You missed your chance.

FEATURES has been used in ebuilds for a loooong time. People were happy with 
it. The only reason it was not properly documented in PMS was because the 
authors didn't agree with it. That's not how you do a standard, but then it 
never was about documenting reality. Now PMS has this hole in it, and instead 
of (1) documenting current behaviour and (2) agreeing on a standard behaviour 
while (3) keeping the historical errata documented ... well, it's kinda, look 
over there ... *runs away*
Not a way to discuss or write a standard, also making things complicated when 
there are known easy ways to fix it. 
> 
> Like, when does this end?  Whenever there's a policy you don't agree with,
> you do whatever you want?  And it's the policy that's the problem?
> 
Well, if everyone else freely ignores it and pointing out that people 
violating the policy has no response I'll consider that policy inactive.

If the Gentoo developers vote with their feet I'm not going to pretend they 
didn't. What you can do then is document what just happened ... maybe ... 
optionally?


> Anyways, this has nothing to do with PMS.  Using FEATURES in the tree was
> frowned upon long before it even existed.  The fact that it wasn't
>  documented as such outside of mailing lists and bug reports is the real
>  bug.
> 
And that usage was tolerated for >2 years. I still don't see what's bad about 
using things as they are, but if people now decide that we need to do complex 
dances instead of fixing things I'll just grab a camera and tape it instead of 
complaining. Life is too short to get worked up about such things :)



  reply	other threads:[~2009-11-04  8:26 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
2009-11-03 22:28       ` Patrick Lauer
2009-11-04  0:11         ` [gentoo-dev] " Ryan Hill
2009-11-04  8:26           ` Patrick Lauer [this message]
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=200911040926.11069.patrick@gentoo.org \
    --to=patrick@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