[tex-live] What's the point of providing a package-level remove feature if nothing can be uninstalled individually?

Siep Kroonenberg siepo at cybercomm.nl
Tue Apr 4 22:12:25 CEST 2017

On Mon, Apr 03, 2017 at 05:00:12AM +0300, Daniel 3ICE Berezvai wrote:
> Hi,
> This is a TeX Live Manager 2016 UX bug report / plea for help, in the form
> of a question (→subject). Or am I using the 'Remove' button wrong?
> More details: Everything I tried to delete ended up being needed by some
> kind of "collection", and upon trying to delete an entire collection I was
> informed that those collections are in turn needed by various "schemes",
> ultimately leading to "scheme-full" through some dependency chain. So I
> removed scheme-full to get rid of the root dependency, but of course that
> uninstalled every single package (and took hours to run).
> Favoring Lite, Portable apps, I'm not happy with a 5Gb default install and
> over 100k files. I wanted to cherry pick the available packages; at first
> pass keeping everything I don't know if I absolutely do not need. Only
> getting rid of various universities' templates, subjects I'm not interested
> in, excess fonts, glyphs, and support for languages I do not speak. Going
> in alphabetical order, I got tired of reading descriptions and checking
> boxes after reaching packages that begin with a letter "c", so I hit the
> Remove button.

>From the command-line:

tlmgr remove --no-depends <whatever>

But you would have done better using the advanced installer, which
lets you pick a smaller scheme and then refine your selection at the
collections level.

Siep Kroonenberg

More information about the tex-live mailing list