From: "yarl baudig" <yarl-baudig@mailoo.org>
To: mail@nicolasgoaziou.fr
Cc: 59354@debbugs.gnu.org
Subject: [bug#59354] [PATCH] gnu: Add texlive-mathdots.
Date: Sun, 20 Nov 2022 17:24:18 +0100 (CET) [thread overview]
Message-ID: <ea-mime-637a54b2-3b3-25629244@www.mailo.com> (raw)
In-Reply-To: <87v8n9ocf8.fsf@nicolasgoaziou.fr>
> >> This doesn't look like a trivial package since it contains a ".ins"
> >> file. You need to generate the ".tex" and ".sty" files from it.
> >>
> > I think it is, "tex/generic/mathdots/" in tug repo contains ".tex" and
> ".sty" and if I compile, they are here.
> > First texlive package I package. I tried `guix import texlive
> > mathdots` then amended by looking at other texlive packages. Please
> > show me if I am wrong.
>
> "guix import texlive mathdots" output doesn't include "#:trivial? #t"
> for a reason. You need to take a longer path and generate runfiles from
> the ".ins" file ; see e.g., "texlive-capt-of".
>
> Regards,
> --
> Nicolas Goaziou
>
Thank you.
I saw that "guix import texlive mathdots" doesn't include "#:trivial? #t" But I still don't see why it is not effectively a trivial package. As I told you, the ".tex" and ".sty" are already in the TUG repo. And with the package as I defined it (as trivial), when you build it, you get the "mathdots.sty" and "mathdots.tex". No need to compile because, whereas there is a ".ins" file, ".sty" and ".tex" are already compiled and distributed, along the ".ins". Right?
next prev parent reply other threads:[~2022-11-20 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 10:20 [bug#59354] [PATCH] gnu: Add texlive-mathdots Yarl Baudig
2022-11-19 9:32 ` Nicolas Goaziou
2022-11-19 15:02 ` yarl baudig
2022-11-20 15:47 ` Nicolas Goaziou
2022-11-20 16:24 ` yarl baudig [this message]
2022-11-20 16:46 ` Nicolas Goaziou
2022-11-20 17:16 ` yarl baudig
2022-11-19 15:02 ` yarl baudig
2022-11-21 14:16 ` Yarl Baudig
2022-11-21 22:21 ` bug#59354: " Nicolas Goaziou
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea-mime-637a54b2-3b3-25629244@www.mailo.com \
--to=yarl-baudig@mailoo.org \
--cc=59354@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).