public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for advanced useflag-syntax
Date: Mon, 07 Aug 2006 10:58:17 +0000	[thread overview]
Message-ID: <44D71CC9.1030300@gentoo.org> (raw)
In-Reply-To: <20060807141821.GI25236@nibiru.local>

Enrico Weigelt wrote:
> * Paul de Vrieze <pauldv@gentoo.org> schrieb:
> 
> <snip>
> 
>>> Well, I don't consider reducing complexity "frivolous" ;-o
>> Which reduction for which complexity? Do you want to bring everyone's 
>> systems to a grinding halt, just because you can't understand the 
>> "complexity" of useflags. 
> 
> I just want to keep things simple. We're talking about introducing
> new (additional) logic. This has to be maintained. And it doesn't 
> actually *solve* the problem which is this discussion was started.
> 
> Rember: we started with the thesis, "grandma wants graphical 
> frontends whereever possible". This is in fact not an technical 
> issue, instead a matter of personal taste, or lets say, an individual
> system configuration. Grandma wants to click, okay, so she should 
> use graphical applications. She's not interested what sits behind, 
> she just wants to have a buch of applications. And she also doesn't
> wann have anything to do with emerge and useflags. She just wants
> to have a choice between a bunch of end-user applications. 
> That's the job of an Grandma-(sub-)distro.
> 

Bad example, as Gentoo generally requires knowledge of the system and
the command line interface; unless you think grandma can update her
toolchain properly with no issues.  I don't think anyone at this point
would hand Gentoo to grandma; and I don't think anyone has that goal.
Mostly we just want an easy to maintain system.  See that word,
maintain; generally means the maintainer knows what they are doing.

> Okay, let's say we want to intruduce an meta-useflag for "GUI"
> (although having additional GUIs in the same package as the 
> backend isn't what I consider clean design). If there's just *one*
> than it's easy - just an alias. But what's if we have more ?
> Who makes the decision, which one to take ? Based on what rules ?
> 

The packages maintainer for Gentoo typically makes the choice on how
something is deployed in Gentoo.

>> Useflags are one of the distinguishing features of gentoo. 
> 
> Yes. For optional features. Additional programs aren't features of
> some other program, but additional programs. 

I would gather for many packages that a gui is a optional feature.
Also this is not a hard and fast rule (and was never meant to be).

> 
> <snip>
> 
>> It is also against the gentoo philosophy of offering software the 
>> way upstream provides it.
> 
> Ah, and this philosophy is more important than quality and 
> maintainability ?

This *philosophy* is a core value of gentoo.  That would be like saying
we should build binary packages for everything because it's easier to
maintain and gives us a higher quality distribution.

Pardon my french, but fuck that.

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-07 15:02 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 11:31 [gentoo-dev] Proposal for advanced useflag-syntax Noack, Sebastian
     [not found] ` <20060803153407.GA19696@nibiru.local>
2006-08-03 18:38   ` Luca Barbato
     [not found]     ` <20060807131642.GF25236@nibiru.local>
2006-08-07 13:40       ` Paul de Vrieze
2006-08-07 14:18         ` Enrico Weigelt
2006-08-07 10:58           ` Alec Warner [this message]
2006-08-07 16:40           ` [gentoo-dev] " Duncan
2006-08-07 21:08           ` [gentoo-dev] " Paul de Vrieze
2006-08-08 10:30             ` Enrico Weigelt
2006-08-08 10:39               ` Simon Stelling
2006-08-08 10:58                 ` Enrico Weigelt
2006-08-08 10:57               ` Jakub Moc
2006-08-04  7:54   ` Simon Stelling
2006-08-04  9:01     ` Brian Harring
2006-08-07 13:48       ` Enrico Weigelt
2006-08-07 14:08         ` Stephen P. Becker
2006-08-08  1:44         ` W.Kenworthy
2006-08-08  2:14           ` Mike Frysinger
2006-08-08 10:34             ` Enrico Weigelt
2006-08-08  2:50           ` Donnie Berkholz
2006-08-08 10:40             ` Enrico Weigelt
2006-08-08 12:37               ` Jan Kundrat
2006-08-08 14:50                 ` Enrico Weigelt
2006-08-08 15:06                   ` Lance Albertson
2006-08-08 20:17                     ` Enrico Weigelt
2006-08-08 20:37                       ` Lance Albertson
2006-08-08 20:46                       ` Jan Kundrát
2006-08-08 21:22                       ` Curtis Napier
2006-08-08 15:12                   ` Thomas Cort
2006-08-08 20:22                     ` Enrico Weigelt
2006-08-08 21:02                       ` Richard Fish
  -- strict thread matches above, loose matches on Subject: below --
2006-08-04  6:21 AW: " Noack, Sebastian
2006-08-07 13:26 ` Enrico Weigelt
2006-08-07 14:53   ` Thomas Cort
2006-08-07 18:48     ` Enrico Weigelt
2006-08-07 20:09   ` Marius Mauch
2006-08-07 21:14     ` Paul de Vrieze
2006-08-07 15:04 AW: " Noack, Sebastian
2006-08-07 20:18 ` Enrico Weigelt

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=44D71CC9.1030300@gentoo.org \
    --to=antarus@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