Ticket #161 (closed enhancement: wontfix)

Opened 15 years ago

Last modified 13 years ago

Make texlive install more quickly.

Reported by: wdc Owned by:
Priority: low Milestone: The Distant Future
Component: installer Keywords:
Cc: Fixed in version:
Upstream bug:  DebianBug:485866


The install of texlive performs activities such as


as every package is installed rather than setting a trigger to perform them once at the end of all package installs.

This causes the texlive install to take far longer than it ideally should.

It would be nice if we could help the upstream debian integrator of texlive to produce a more efficient install.

Broder has also cooked up a hack to do some triggerizing:

Consensus is that we'd prefer to work with upstream rather than having our own local hack.

Change History

comment:1 Changed 15 years ago by broder

  • Upstream bug set to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485866

comment:2 Changed 15 years ago by broder

  • Upstream bug changed from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485866 to DebianBug:485866

comment:3 Changed 15 years ago by jdreed

Here's an idea:

We currently install texlive-full. I bet we really don't need half the stuff in texlive-full. What if we create our own metapackage that depends on what we (arbitrarily) deem to be "important" or "popular" parts of texlive? People who want additional languages or macros can install packages themselves, either on their own machine, or in the cluster chroot.

I think that would be a good local fix that isn't really a hack and doesn't preclude collaboration with upstream, but should still speed up installation noticeably.

comment:4 Changed 15 years ago by jdreed

  • Component changed from -- to installer
  • Milestone set to The Distant Future

comment:5 Changed 14 years ago by geofft

TeXLive seems not to be a significant part of the time-taking part of the install any more. Am I just being easily distractable while doing installs, or do other people concur and can we WONTFIX this?

comment:6 Changed 13 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to wontfix

I agree with Geoff. I think we "fixed" this by inventing dual-core processors or something.

Note: See TracTickets for help on using tickets.