public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tobias Klausmann <klausman@schwarzvogel.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: USE flag transition: tetex and latex
Date: Tue, 6 Nov 2007 15:42:24 +0100	[thread overview]
Message-ID: <20071106144224.GB17407@eric.schwarzvogel.de> (raw)
In-Reply-To: <20071106141327.176c2b65@gentoo.org>

Hi! 

On Tue, 06 Nov 2007, Christian Faulhammer wrote:
> > tetex-alike distribution. So, imho, in that case a kpathsea useflag
> > would make more sense; but I doubt such a useflag name will speak by
> > itself.
> 
>  Yes, we should introduce tex, latex and kpathsea USE flags.  Anyone?

As long as the description of the USE flag (such as by euse -i)
is usefule (and *not* the equally omnipresentand useless  "foo -
enables foo support"), I see no trouble in using it.

In this case I'd go for:
kpathsea - Enable (La)TeX integration.

I do understand that sometimes a given USE flags description
can't be unified. USE="foo" might enable very different things in
different packages. But then, global USE flags are the only once
where this is a concern.

For example, take mplayer's (local) USE flag "vidix". euse -i isn't
exactly helpful: "Support for vidix video output"

IMHO, it'd better be "Support X11 DGA video output using the
vidix interface"

One might argue that I should know the stuff I want but what if
I'd want the support for foo if I only knew about it?

Also, my (arguably not very good) example illustrates how extra
keywords might help the user find out what exactly vidix is using
Google.

Regards,
Tobias

PS: Yes, I've read the recend mp3/mp3{de,en}code discussuion,
same problem, actually.
-- 
In the future, everyone will be anonymous for 15 minutes.
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-11-06 14:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31  7:03 [gentoo-dev] USE flag transition: tetex and latex Christian Faulhammer
2007-10-31 10:38 ` Alexis Ballier
2007-11-01  8:10   ` [gentoo-dev] " Steve Long
2007-11-06 13:13   ` Christian Faulhammer
2007-11-06 14:42     ` Tobias Klausmann [this message]
2007-11-06 14:46       ` Christian Faulhammer
2007-11-06 16:44         ` Tobias Klausmann
2007-11-07  8:13     ` Alexis Ballier
2007-11-10 14:16       ` Christian Faulhammer
  -- strict thread matches above, loose matches on Subject: below --
2007-11-07 13:09 Ferris McCormick
2007-11-10  2:03 ` Robert Buchholz
2007-11-10 11:04   ` Alexis Ballier
2007-11-10 14:12 ` Christian Faulhammer

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=20071106144224.GB17407@eric.schwarzvogel.de \
    --to=klausman@schwarzvogel.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