public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] USE Flags
Date: Sun, 20 Mar 2005 23:21:39 +0100	[thread overview]
Message-ID: <20050320232139.7eea3df7@eusebe> (raw)
In-Reply-To: <200503202201.26459.pauldv@gentoo.org>

On Sun, 20 Mar 2005 22:01:18 +0100
Paul de Vrieze <pauldv@gentoo.org> wrote:

> I'll add some nice tag to support this.

I'm sorry to insist, but is there something wrong with using
use.local.desc, as i've proposed in bug #84884? I don't understand
the rational for choosing metadata.xml. In my opinion, it makes
this detailed description less likely to be written (more
complex syntax, whereas the one of .desc file is already
well-known), and less likely to be read (lack of user tools
whereas there are plently for use.local.desc, which would need at
most small trivial changes, if any). 

Also, take the following scenario:

 - use.local.desc has: 
"cat/pkgA:foo - adds support for libfoo as a replacement of \
libbar. Do not enable it but if you really know what you do."

 - then comes cat/pkgB, which also support libfoo:
"cat/pkgB:foo - adds support for libfoo, for playing .foo files"

 - And more packages start supporting libfoo, thus "foo" becomes 
a global flag:
"foo - adds support for libfoo"
With the "metadata.xml" approach, that will require moving the
existing descriptions from use.local.desc to the various xml
files.  At the contrary, with the "keep it in use.local.desc"
approach, no additional work is required... 


So could someone explain me that choice?

Thanks,

-- 
TGL.
--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-03-20 22:22 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
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 [this message]
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=20050320232139.7eea3df7@eusebe \
    --to=degrenier@easyconnect.fr \
    --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