emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#27217: closed (texlive is too big)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#27217: closed (texlive is too big)
Date: Tue, 15 Jan 2019 15:35:01 +0000

Your message dated Tue, 15 Jan 2019 16:34:32 +0100
with message-id <address@hidden>
and subject line Re: bug#27217: texlive is too big
has caused the debbugs.gnu.org bug report #27217,
regarding texlive is too big
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
27217: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27217
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: texlive is too big Date: Sat, 03 Jun 2017 21:03:49 +0200 User-agent: mu4e 0.9.18; emacs 25.2.1
Currently, we offer the complete texlive distribution in a single
package that weighs several gigabytes.  This causes several problems:

* it’s much too heavy a dependency for packages
* it takes a long time to download
* it takes a long time to compress the substitute
* a user who only wants to compile a simple PDF needs to put up with
  installing the complete texlive distribution.

The purpose of this bug report is to keep track of the remaining issues
in splitting up texlive.

This is the current status (in my local branch):

* we have a texlive importer that fetches description and version info
  from CTAN but downloads from the texlive SVN.  This is because CTAN
  does not store versioned tarballs.

* we have a new texlive-build-system that can compile TeX packages in
  “.ins” + “.dtx” format

* the build system works fine for creating individual packages for the
  LaTeX required package set.

* these packages are sufficient to build the documentation of the
  package “fastcap” in DVI and PDF format

What’s missing?

Currently, one needs to set a lot of environment variables to use these
separate packages.  For “fastcap” I needed to set “DVIPSHEADERS” (to
find “tex.pro”), “TFMFONTS” (for compiled metafont files), “TEXFORMATS”
(for the compiled “latex.fmt”), and “TEXINPUTS” (for all directories
containing tex source files).  Setting these variables manually is
really tedious.

How can we set them automatically?  A simple idea is to provide a
procedure “texlive-union” that takes texlive packages and produces a
wrapped variant of the tools in “texlive-bin” that run inside an
environment where these variables are set.

It is also not clear how users should install texlive from countless
separate packages.  We should provide different sets of packages for
variants like texlive-minimal up to texlive-most.  We may also want to
support installation of individual packages by providing a profile hook
(e.g. when a user only wants texlive-minimal with the gbrief package).

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net




--- End Message ---
--- Begin Message --- Subject: Re: bug#27217: texlive is too big Date: Tue, 15 Jan 2019 16:34:32 +0100 User-agent: mu4e 1.0; emacs 26.1
Ricardo Wurmus <address@hidden> writes:

> We may also want to
> support installation of individual packages by providing a profile hook
> (e.g. when a user only wants texlive-minimal with the gbrief package).

A profile hook has been added with commit
743497b5650713e082f4775a3b7dfd03babc8191.  Users may want to start by
installing “texlive-base” and then add packages to their profile as
needed.

I’m closing this bug now.

--
Ricardo



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]