From: Daniel Goller <morfic@gentoo.org>
To: gentoo-dev@gentoo.org
Cc: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] USE Flags
Date: Thu, 10 Mar 2005 19:05:13 -0600 [thread overview]
Message-ID: <4230EEC9.7030709@gentoo.org> (raw)
Message-ID: <20050311010513.YrfohudUMSP5AjSoI0bHhEkMVMqEpzzFDiBqtxN0g5Q@z> (raw)
In-Reply-To: <422F311B.7010102@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
Fabian Zeindl wrote:
> Martin Schlemmer wrote:
>
>> On Wed, 2005-03-09 at 14:23 +0100, Markus Nigbur wrote:
>>
>>> On Wed, 2005-03-09 at 14:00 +0100, Marius Mauch wrote:
>>>
>>>> On Wed, 09 Mar 2005 13:38:53 +0100
>>>> Fabian Zeindl <fabian.zeindl@gmx.at> wrote:
>>>>
>>>>
>>>>> Hi
>>>>>
>>>>> I startet a discussion a time ago about new use flag explanations in
>>>>> ebuilds:
>>>>> http://thread.gmane.org/gmane.linux.gentoo.portage.devel/618
>>>>>
>>>>> Can anyone tell me whether this is going to be implemented?
>>>>
>>>>
>>>> As I said, this has to be done in metadata.xml (and not in ebuilds) and
>>>> so far the DTD isn't changed. Paul, any news on this?
>>>>
>>>> Marius
>>>>
>>>
>>> That's one of those things that should be easy to establish and result
>>> in a huge benefit for everyone. I'd probably the first who hacks
>>> detailed descriptions for every flag my maintained packages have.
>>>
>>> If the only thing that prevents the implementation from being realized,
>>> is lack of time or lack of man power, feel free to contact me.
>>>
>>
>>
>> Sounds more like a PITA to me, but I wont object out of that
>> principal :]
>
>
> What's a PITA?
Pain In The Hintern
>
> fabian
>
> --
> Musik kann nicht illegal sein: www.fairsharing.de
>
> I prefer signed/encrypted Mail:
> http://stud3.tuwien.ac.at/~e0327380/pub_key.asc
> Fingerprint: CFE8 38A7 0BC4 3CB0 E454 FA8D 04F9 B3B6 E02D 25BA
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-03-11 2:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 12:38 [gentoo-dev] USE Flags Fabian Zeindl
2005-03-09 13:00 ` Marius Mauch
2005-03-09 13:23 ` Markus Nigbur
2005-03-09 17:13 ` Martin Schlemmer
2005-03-09 17:23 ` Fabian Zeindl
2005-03-09 18:19 ` Benno Schulenberg
2005-03-10 0:56 ` Mike Frysinger
2005-03-10 18:25 ` Benno Schulenberg
2005-03-10 18:37 ` Mike Frysinger
2005-03-10 20:16 ` Drake Wyrm
2005-03-11 1:05 ` Daniel Goller [this message]
2005-03-11 1:05 ` Daniel Goller
2005-03-11 19:06 ` Thomas de Grenier de Latour
2005-03-11 19:17 ` Fabian Zeindl
2005-03-20 21:01 ` Paul de Vrieze
2005-03-20 22:21 ` Thomas de Grenier de Latour
2005-03-21 5:11 ` Marius Mauch
2005-03-21 8:56 ` Thomas de Grenier de Latour
2005-03-21 21:55 ` Thomas de Grenier de Latour
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 21:34 [gentoo-dev] USE flags A. Craig West
2003-10-22 22:36 ` Dhruba Bandopadhyay
2003-10-22 22:58 ` david
2003-10-23 0:41 ` Chris Gianelloni
2003-10-23 8:46 ` Spider
2003-10-23 8:49 ` Patrick Kursawe
2003-10-23 9:14 ` Paul de Vrieze
2003-10-23 11:39 ` Philippe Coulonges
2003-10-23 12:20 ` Christian Birchinger
2003-10-23 15:59 ` Spider
2003-10-23 19:27 ` Masatomo Nakano
2003-10-23 0:40 ` Chris Gianelloni
2001-09-23 10:38 Viktor Lakics
2001-09-23 10:50 ` Martin Schlemmer
2001-09-23 12:36 ` Dan Armak
2001-09-23 12:15 ` Karl Trygve Kalleberg
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=4230EEC9.7030709@gentoo.org \
--to=morfic@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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