Bug#334611: tetex-bin: Please compile xdvi with lesstif2
Adrian Bunk <bunk@stusta.de> wrote:
> On Tue, Oct 25, 2005 at 06:04:43PM +0200, Frank Küster wrote:
>>
>> In this case, the main motivation is not disk space. Rather, it is
>> bandwidth and, in particular, installation time (the latter being
>
> If the only difference of tetex-bin-nox is that the binaries depending
> on X11 libraries are omitted this saves you perhaps 1% or 2% of a
> tetex-bin + tetex-base installation.
The difference is that the buildd's won't need to download and install
several xlibs just because they need to run pdflatex or latex;dvips
during a package build. Not to mention that we plan to make tetex-base
considerably smaller.
>> probably more important on buildds) for packages that Build-Depend on
>> tetex-bin, and the wish not to install xlibs on a server (that creates
>
> If someone needs the "convert" program he simply adds a build dependency
> on imagemagick and look how much this pulls in.
>
> You can optimize for many different things, and I'd personally consider
> the user-visible points mirror and CD space and the number of packages
> in the archive more important than a few seconds speedup at build time.
Other people have requested that, and I cannot judge who has more
experience with buildds. On the other hand, I can very well understand
the wish to have a server running that is able to produce PDF from *TeX
source, but has no trace of X11 installed.
>> PDF files) for tetex-bin as a Depends or for direct installation.
>
> The only real problem eith installing X11 libraries on a server is in
> the case of limited space. And if the space is that limited (which is
> quite rare), a distribution like Gentoo is a better choice.
Others would advocate that there are good reasons not to have X on a
server. I don't want to argue about that, I simply hear it. And it
adds one more argument in favor of a -nox.
> The question is for how many of these > 95% a few MB of disk space do
> matter compared to the confusion because of having to choose from many
> packages a subset sufficient for their usage.
Avoiding confusion is a question of clever naming, Dependencies and a
transition strategy, isn't it?
> And if they get teTeX through a task, they will anyways most likely get
> everything.
There's no task: TeX any more. That is an important point to consider.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Reply to: