public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Faulhammer <opfer@gentoo.org>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: USE flag transition: tetex and latex
Date: Tue, 6 Nov 2007 14:13:27 +0100	[thread overview]
Message-ID: <20071106141327.176c2b65@gentoo.org> (raw)
In-Reply-To: <20071031113819.1a7f4a8a@toz.strangled.net>

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

Alexis Ballier <aballier@gentoo.org>:

> > 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:

 After some more calm minutes thinking about it:

> 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)

 Agree.

> 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.

 Yes, we should introduce tex, latex and kpathsea USE flags.  Anyone?

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://www.faulhammer.org/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-11-06 13:16 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 [this message]
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=20071106141327.176c2b65@gentoo.org \
    --to=opfer@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