From: "Jan Kundrát" <jkt@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for advanced useflag-syntax
Date: Tue, 08 Aug 2006 22:46:10 +0200 [thread overview]
Message-ID: <44D8F812.5020909@gentoo.org> (raw)
In-Reply-To: <20060808201725.GA1477@nibiru.local>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Enrico Weigelt wrote:
>> Opening an ebuild and reading it must be hard.
>
> Not what I asked. I'm talking about what an user can expect to get.
> You don't expect every user to look trough each ebuilt, seriously ?
>
> And, in case of Xorg, the individual needs may very deeply.
> Some applications need just Xlib, some Xaw, others maybe some
> extensions, etc.
>
> If you would put evrything in one monolithic package you would,
> in the end, need one useflag per library. Or you loose the ability
> to build the system for your special needs. Most times you'll get
> much, much stuff you won't ever need. Is this compatible with
> the gentoo philosphy ?
Please wake up. We have modular X.org now so just move along and b*tch
about anything else. If you really feel like this is the best thing you
can do for Gentoo development, please provide a procmail rule that kills
all your -dev mails along with relevant replies.
Cheers,
-jkt
--
cd /local/pub && more beer > /dev/mouth
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-08-08 20:49 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
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 [this message]
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=44D8F812.5020909@gentoo.org \
--to=jkt@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