From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] How to provide a recent TeXLive for Gentoo for our users?
Date: Mon, 26 Mar 2018 11:57:49 +0200 [thread overview]
Message-ID: <2af5b93d-ee22-388d-96ba-f3a32f0178e5@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1307 bytes --]
Dear all,
there was a question on the tex@gentoo ml from a user, who needs a very
recent TeXLive in order to be compatible with other setups.
This is also very important, for users of the more recent programs like
lualatex. Many packages do not work properly in the unfixed old version.
An installation via tlmgr provides many updates per day, but
our distributed TeXLive is unfortunately always behind.
Typically TeXLive on gentoo is 6-12 months behind upstream, because we
have to bump a lot manually.
One solution would be more powerful scripts, which update the TeX
ebuilds, but the ticket is open since 2005.
https://bugs.gentoo.org/85411
On one Gentoo system I installed therefor TeXLive via tlmgr and added
all provided packages in package.provided like this:
/etc/portage/profile/package.provided/texlive.provided
[..]
dev-tex/xcolor-9999
dev-tex/latexdiff-9999
dev-tex/glossaries-9999
dev-tex/biblatex-9999
dev-tex/biber-9999
dev-tex/bibtexu-9999
app-text/texlive-core-9999
This is not a very nice solution, but it works so far. One difficulty
is, that there is no 1:1 relation between the texlive distribution and
dev-texlive/* at the moment.
How can we enable our users to run a recent TeXLive in a clean way?
Ideas are welcome.
--
Best,
Jonas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next reply other threads:[~2018-03-26 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 9:57 Jonas Stein [this message]
2018-03-26 12:38 ` [gentoo-dev] How to provide a recent TeXLive for Gentoo for our users? Alexis Ballier
2018-03-26 18:07 ` Jonas Stein
2018-03-26 19:16 ` Alexis Ballier
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=2af5b93d-ee22-388d-96ba-f3a32f0178e5@gentoo.org \
--to=jstein@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