From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] USE flag transition: tetex and latex
Date: Wed, 31 Oct 2007 11:38:19 +0100 [thread overview]
Message-ID: <20071031113819.1a7f4a8a@toz.strangled.net> (raw)
In-Reply-To: <20071031080355.198fa5d3@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
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.
Alexis.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-31 10:41 UTC|newest]
Thread overview: 9+ 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 [this message]
2007-11-01 8:10 ` [gentoo-dev] " Steve Long
2007-11-06 13:13 ` 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
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=20071031113819.1a7f4a8a@toz.strangled.net \
--to=aballier@gentoo.org \
--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