From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
Guix Devel <guix-devel@gnu.org>
Subject: Re: Question about packaging TexLive
Date: Wed, 19 Apr 2023 13:47:16 +0200 [thread overview]
Message-ID: <87ildsqekb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87o7nkqkap.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 19 Apr 2023 11:36:46 +0200")
Ricardo Wurmus <rekado@elephly.net> writes:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> 1. "#:trivial? #t" means we're giving up generating ".sty" files from
>> source;
>
> Trivial should only ever be used for packages where there aren’t any
> sources to build from.
We are on the same length.
However, some packages do use "#:trivial #t" even though they should
not, e.g., `texlive-latex-marginfix'. My point is that we should not
make "#:trivial #t" the default, assuming that was a possibility
stemming from Simon's question.
>> 2. Some affected packages are also missing propagated inputs (e.g.,
>> texlive-latex-graphics for texlive-latex-fncychap);
>
> Correct. The old importer didn’t know about dependencies. The newer
> importer uses tlpdb to get a list of dependencies.
AFAIU, this is not sufficient. All dependencies do not appear in
"texlive.tlpbd". For example, `texlive-halloweenmath' has no "depend"
entry in the tlpbd. Yet, it requires both texlive-amsmath and
texlive-pict2e (i.e., "halloweenmath.sty" contains
"\RequirePackage{amsmath,pict2e}").
So, unless I'm mistaken, most dependencies have to be resolved manually.
> All packages must be checked for completeness. All new packages I’ve
> added have been checked. All old packages must be checked before
> renaming them. The way to check them is to build them and then check
> the outputs with something like this:
>
> --8<---------------cut here---------------start------------->8---
> ,use (guix import texlive)
> ,pp (files-differ? "/gnu/store/…-texlive-amsfonts-fixed-59745/share/" "amsfonts")
> --8<---------------cut here---------------end--------------->8---
>
> This compares outputs with tlpdb.
I use this valuable tool, but this is somewhat tedious. Could this
become a test in the linter?
> Note that simple-texlive-package is far from perfect. We have many
> tex packages that require excessive workarounds to ensure that files end
> up in the correct location and that superfluous files are removed.
> simple-texlive-package should eventually take care of all of this, but I
> haven’t been able to make time to work on it.
We may need to update more Texlive packages to get a better grasp of the
changes required in `simple-texlive-packages'. When doing such updates,
I mostly copy and paste definition from previously updated packages,
which is a good thing. However, some translations seem complicated.
> All this work should be done on a separate feature branch.
Agreed.
Regards,
next prev parent reply other threads:[~2023-04-19 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 8:47 Question about packaging TexLive Simon Tournier
2023-04-19 9:14 ` Nicolas Goaziou
2023-04-19 9:36 ` Ricardo Wurmus
2023-04-19 11:47 ` Nicolas Goaziou [this message]
2023-04-19 11:50 ` Andreas Enge
2023-04-19 11:56 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ildsqekb.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.