Bug#464586: texlive packages' dependencies (was: Bug#464586: n/a, really)
On Fr, 15 Feb 2008, Richard Hartmann wrote:
> There is only one way to really find that out, but which would not be feasible
> without automation. A parser that goes through all packages, looks for includes
> and saves that information into a directed graph. With some visualisation, it
> would be possible to seperate the graph into subgraphs.
Good luck. If you can write one then you have written a new TeX engine.
Please go on and send us the tree ...
Seriously, this is rubbish and will not be fixed. The definition of
depends as given by Frank explains that good enough.
I intent to close thi
> Of course, cyclic paths would make that approach harder, the resulting
> meta-packages larger or as large as the full set of nodes.
> Also, this does not account for which packages are popular and which are not.
>
> This kind of information would probably be useful at CTAN, as well.
You are used to Debian levels, something which cannot and will not
happen with LaTeX. Most authors not even know the correct dependencies
of their packages, and which versions of which package is necessary.
There is no way to do something like CPAN, or better, it was rejected
from ftp-masters when I started packaging TeX Live. I could have made
one Debian package per TL package. But 2000+ new packages was a bit too
much for Debian.
And it is absolutely USELESS to do it like this.
Enough, I am bored.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at> Vienna University of Technology
Debian Developer <preining@debian.org> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
PEORIA (n.)
The fear of peeling too few potatoes.
--- Douglas Adams, The Meaning of Liff
Reply to: