public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: USE flag transition: tetex and latex
Date: Thu, 01 Nov 2007 08:10:31 +0000	[thread overview]
Message-ID: <fgc1er$5ds$2@ger.gmane.org> (raw)
In-Reply-To: 20071031113819.1a7f4a8a@toz.strangled.net

Alexis Ballier wrote:

> Hi,
> 
>> What are we going to do with the global tetex USE flag?
>> app-text/tetex is deprecated in favour of TeXLive which is still hard
>> masked but will be the default TeX distribution in the future.
>> Rename it to tex as TeXLive is based on teTeX? And what about
>> USE=latex? Use a generic tex for it, too?
> 
> 
> I had been thinking about it and am not sure what would be the best
> option:
> Some packages use the tetex useflag to enable some latex support, in
> which case a latex useflag should be fine. (e.g. doxygen is the first
> one I found that seems to be in that case)
> Some others use it to enable kpathsea support, where tetex is the
> historical distribution that provides it for us. From quickly digging
> into lcdf-typetools code for ex., it seems it is used there to locate
> files and update the kpathsea files so that other apps using kpathsea
> will see the changes it has made. That way it integrates with a
> 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.
> 
The flag sounds ideal to me; there are plenty of other flags which just
say "Use lib N to do X" and for people who know the area, the lib is known,
and for newbs they normally should know about it. (Half the educational
value in gentoo is finding out about other software like that imo.)


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-11-01  8:13 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   ` Steve Long [this message]
2007-11-06 13:13   ` [gentoo-dev] " Christian Faulhammer
2007-11-06 14:42     ` Tobias Klausmann
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='fgc1er$5ds$2@ger.gmane.org' \
    --to=slong@rathaus.eclipse.co.uk \
    --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