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: Mon, 21 Mar 2005 09:56:01 +0100	[thread overview]
Message-ID: <20050321095601.4b2c7746@eusebe> (raw)
In-Reply-To: <20050321061128.6b7f0b64@sven.genone.homeip.net>

On Mon, 21 Mar 2005 06:11:28 +0100
Marius Mauch <genone@gentoo.org> wrote:

> (no tool support for either solution)

Well, actually i've put some bits of code in the bugreport I've
mentioned above, so there is tool support for the use.local.desc
solution (equery and emerge). That was more to demonstrate how
easy it was to implement tho, and i agree it's not the only point
of the discussion.

> use.local.desc for package-specific short descriptions (like at
> the moment) and metadata.xml for longer detailed descriptions
> if required

That sounds like a good idea. So, to summarize (just to check
i've understood your proposal):

 - users should know when a flag is really a must-have for a
given package, or is at the contrary not advised, things like
that. That kind of quick hints, warnings, and other answers to
obvious questions like "Is DVD support by mplayer better with the
'dvdread' flag?" only require short notes (one sentence) in
general.  But what is important is that they get written whenever
there is something to say about a flag which is not already in
use.desc (because package-specific), and that they are easily
accessible for the user.  Here, use.local.desc seems better,
because there is no such thing as an "echo >>" to drop a quick
note somewhere, and because it doesn't require complex code or
access to multiple files to get optionaly displayed by emerge in
pretend mode.

 - user might sometimes wonder what is the "libfoo" that the "foo"
flag description ("add support for libfoo") talks about. That may
require a long description (one paragraphe), which don't need to
be in use.local.desc.  Metadata.xml is fine here, since anyway
that's the kind of things you write using a text editor. 

That raises on more question tho: if someone wants to write a
long description for a global flag, where does he do it?

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


  reply	other threads:[~2005-03-21  8:56 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
2005-03-21  5:11       ` Marius Mauch
2005-03-21  8:56         ` Thomas de Grenier de Latour [this message]
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=20050321095601.4b2c7746@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