public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexandre Buisse <nattfodd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Future of tetex
Date: Sat, 27 May 2006 11:36:05 +0200	[thread overview]
Message-ID: <20060527093556.GA7325@ubik> (raw)
In-Reply-To: <44771213.7070205@gentoo.org>

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

On Sat, May 27, 2006 at 11:03:36 +0200, Marcus D. Hanwell wrote:
> > 
> > Now for the exciting (but time consuming) news:
> > 
> > The road to a stable TeXLive in Gentoo:
> > 
> > 1. Stabilize tetex-3.0_p1[3]. We are almost done, there are very few
> > real bugs left, and tetex-3.0_p1 is already much more stable than
> > tetex-2 ever was. I hope this will happen in the next month.
> 
> This is long overdue - again if I can help please let me know. I use
> this all the time and have been doing so for the last year. Do you have
> a stabilisation tracker bug set up for this yet?

Yes, see http://bugs.gentoo.org/show_bug.cgi?id=124511

> > 
> > 3. Create a TeXLive ebuild and put it onto ~arch and have ~arch user
> > switch over.
> > This requires us to figure out how to create a texmf-tree. In the past
> > Thomas Esser created a very solid (although containing rather old
> > versions) texmf-tree with packages taken from ctan[5].
> > There are several possibilities:
> > 3.1 Create our own texmf-tree (can largely be automated by scripting).
> > 3.2 Use MikTeX package manager[6] which was ported to Linux.
> > 3.3 Use something similar to the g-cpan.pl script used by perl, to
> > install packages from ctan[7].
> > I haven't evaluated the possibilities yet, but comments are more than
> > welcome!
> > 
> I would favour option 3.1 personally, and it would be great to keep our
> LaTeX packages more up to date as I sometimes have to manually update
> these packages.

I agree, but the question is to see how far we can automate the process.
CTAN is a really large database and even the MikTeX package manager has
only a fraction of it.

Regards,
/Alexandre
-- 
Hi, I'm a .signature virus! Please copy me in your ~/.signature.

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-05-27  9:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26 11:02 [gentoo-dev] Future of tetex Martin Ehmsen
2006-05-26 13:16 ` Diego 'Flameeyes' Pettenò
2006-05-26 14:34 ` Marcus D. Hanwell
2006-05-27  9:36   ` Alexandre Buisse [this message]
2006-06-13 13:51 ` [gentoo-dev] " Gabriel Lavoie
2006-06-13 15:03   ` Martin Ehmsen
2006-06-13 15:14     ` Gabriel Lavoie
2006-06-13 15:33       ` Martin Ehmsen
2006-08-25 15:15         ` Gabriel Lavoie
2006-08-25  0:00           ` Christian 'Opfer' Faulhammer
2006-08-28 19:13             ` Gabriel Lavoie

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=20060527093556.GA7325@ubik \
    --to=nattfodd@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