public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for advanced useflag-syntax
Date: Mon, 7 Aug 2006 22:18:11 +0200	[thread overview]
Message-ID: <20060807201811.GN18220@nibiru.local> (raw)
In-Reply-To: <7B97065F451A23458ED0C63B4CA5A2EA7C4A6F@SRV-EXCHANGE.AUTOonline.local>

* Noack, Sebastian <S.Noack@AUTOonline.de> schrieb:

<snip>

> Is a need to have dozens of lines in your /etc/portage/package.use 
> a simple approach? Maybe it is, if for you, simplicity means only 
> "less number of lines of code in the core of the application". 
> But wasn't you the one who told me that quantity isn't the same like 
> complexity? Well you could say that only source code and scripts 
> contain logic and therefore numbers of lines in the config files 
> doesn't means complexity, but what do I do by the config files of 
> portage actually? I use them for example to instruct portage to 
> enable useflag A but not for ebuild and useflag B but just for 
> ebuild b. Do you claim that this is no logic?

No, that's just quantity of information. Linear data, just like an
list of addresses or phone numbers. There are no rules in it.

The rules just exist in your mind, not in the portage system.
And if you like to modelize them, it should be done separately 
on top of portage.

Okay, let's assume for a while, we've got your additional rules
in the portage system. Someone has to make the decision about 
which frontends to prefer over others. If it's you, then you'll 
be happy with that, since you'll most likely decide the way you
like, but others may be very unhappy with your decisions. On the
other hand, with anyone else making this decision, there's plenty
risk, you'll be unhappy with his decision.

I see big flamewars coming on that. 
Remember the sunrise affair(s) ? 

<snip>

> > 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.
> 
> That was never the point where "we" started. That was just the point,
> you used to confuse this discussion. 

Maybe I missed something, but this was the first posting I read on
that topic. 

> The grandma scenario should just be a funny example for a requirement 
> of such a advanced portage syntax I could really need on my own systems 
> and I'm not female, but male and not 80 but 18 years old. ;)

IMHO an bad chosen one, as I take such examples seriously.

<snip>

> I know that my proposed syntax isn't a perfect solution. But I think the
> current state of portage isn't a perfect solution, too. And I hoped when
> I started this thread, that we will find together a good solution.

IMHO, the problem isn't yet defined cleanly enough to have a chance
on an good solution.


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-08-07 20:27 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 15:04 AW: [gentoo-dev] Proposal for advanced useflag-syntax Noack, Sebastian
2006-08-07 15:21 ` Luca Barbato
2006-08-07 20:18 ` Enrico Weigelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-04  6:21 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-03 11:31 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
2006-08-07 21:08           ` 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

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=20060807201811.GN18220@nibiru.local \
    --to=weigelt@metux.de \
    --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