From: Ricardo Wurmus <rekado@elephly.net>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 55868-done@debbugs.gnu.org
Subject: bug#55868: [PATCH] gnu: r-prereg: Add TeXLive dependencies.
Date: Fri, 10 Jun 2022 17:57:27 +0200 [thread overview]
Message-ID: <87czfg33sa.fsf@elephly.net> (raw)
In-Reply-To: <YqLuE9XPJjn2UCkZ@noor.fritz.box>
Lars-Dominik Braun <lars@6xq.net> writes:
> Hi Ricardo,
>
>> > + (texlive-updmap.cfg (list texlive-amsfonts texlive-lm))))
>>
>> What’s up with this one? texlive-updmap.cfg isn’t supposed to be
>> propagated. Why is it used with only these two texlive-* packages?
> my understanding was that texlive-updmap.cfg is only useful for font
> packages. Why is it not supposed to be propagated? I looked at
> python-nbconvert as a reference, which does the same thing.
My mistake. I still remember texlive-union, which built a union
directory from its inputs — that union directory and its config file
could not be composed with other files or packages. Propagating it
would have been pointless.
This texlive-union eventually gave way to texlive-updmap.cfg, which only
creates font map files, while propagating its inputs. The font map
files should be usable as is, and since the inputs are propagated the
texlive-base profile hook can generate them anew (together with other
installed texlive-* packages) when needed.
So I guess this is fine after all. Sorry for the noise!
I have applied your patch.
--
Ricardo
prev parent reply other threads:[~2022-06-10 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 12:26 [bug#55868] [PATCH] gnu: r-prereg: Add TeXLive dependencies Lars-Dominik Braun
2022-06-09 15:42 ` Ricardo Wurmus
2022-06-10 7:09 ` Lars-Dominik Braun
2022-06-10 15:57 ` Ricardo Wurmus [this message]
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=87czfg33sa.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=55868-done@debbugs.gnu.org \
--cc=lars@6xq.net \
/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).