GNU bug report logs -
#62570
[PATCH 0/6] Fix name and dependencies of a few Texlive packages
Previous Next
Full log
View this message in rfc822 format
Hello,
Simon Tournier <zimon.toutoune <at> gmail.com> writes:
> On Fri, 07 Apr 2023 at 20:01, Nicolas Goaziou <mail <at> nicolasgoaziou.fr> wrote:
>
>> Unfortunately, there are other old TeXLive packages in this very same
>> sad situation.
>
> Well, one after the other, they will be converted. :-)
Sure thing.
However, correcting myself, as my words were too strong in this
particular case, current "texlive-latex-bigfoot" is not exactly
"broken". Running "./pre-inst-env guix build texlive-latex-bigfoot"
generates the following layout:
/gnu/store/848cbycs3y9gqbc0c6giag1m7a53x32r-texlive-latex-bigfoot-59745
└── share
└── texmf-dist
└── tex
└── latex
└── bigfoot
├── bigfoot.drv
├── bigfoot.sty
├── perpage.drv
├── perpage.sty
├── suffix.drv
└── suffix.sty
6 directories, 6 files
So, ".sty" files are indeed properly installed. There is no
documentation, though. Also, source files are not kept in the store.
There are two approaches going on here. `simple-texlive-package' tries
to provide a tessellation of the full texlive, i.e., if you install
(assuming they are defined in Guix) every standalone texlive package,
you will get the exact full texlive distribution, whereas
`texlive-ref' + `texlive-build-system' tries to generate a minimal (a
bit too minimal considering missing documentation) working system.
I think the old way is error prone.
So, do we (not only the two of us, obviously) agree on the
`simple-texlive-package' approach? If so, what should we do about
"source"?
Regards,
--
Nicolas Goaziou
This bug report was last modified 2 years and 113 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.