all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 69212@debbugs.gnu.org
Subject: [bug#69212] [PATCH RFC 4/4] gnu: Add perl-tex-autotex.
Date: Wed, 22 May 2024 18:55:48 +0200	[thread overview]
Message-ID: <642d0a88a2d6f09603a6a7b3fef9679e739b7ca1.camel@gmail.com> (raw)
In-Reply-To: <87ikz69vae.fsf@nicolasgoaziou.fr>

Am Mittwoch, dem 22.05.2024 um 09:10 +0200 schrieb Nicolas Goaziou:
> Hello,
> 
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> 
> > +   (inputs (list bash-minimal coreutils sed sendmail
> > +                 texlive-scheme-basic))
> 
> Nitpick: even though they are equivalent, I think (texlive-
> updmap.cfg)
> is more appropriate here. As a rule of thumb texlive-scheme-* and
> texlive-collection-* are for users, whereas (texlive-updmap.cfg) is
> for packages.
Good to know.  I'm just unsure which packages to feed it so as to get
all the autotex features (basically to get "what arxiv supports"),
hence why it's blocked atm.

Cheers




  reply	other threads:[~2024-05-22 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17 23:16 [bug#69212] [PATCH RFC 0/4] Add AutoTeX Liliana Marie Prikler
2024-02-17 22:45 ` [bug#69212] [PATCH RFC 3/4] gnu: Add perl-arxiv Liliana Marie Prikler
2024-02-17 22:46 ` [bug#69212] [PATCH RFC 2/4] gnu: Add perl-cam-pdf Liliana Marie Prikler
2024-02-17 22:48 ` [bug#69212] [PATCH RFC 1/4] gnu: Add perl-text-pdf Liliana Marie Prikler
2024-02-17 23:16 ` [bug#69212] [PATCH RFC 4/4] gnu: Add perl-tex-autotex Liliana Marie Prikler
2024-05-22  7:10   ` Nicolas Goaziou via Guix-patches via
2024-05-22 16:55     ` Liliana Marie Prikler [this message]
2024-05-23  9:56       ` Nicolas Goaziou via Guix-patches via

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=642d0a88a2d6f09603a6a7b3fef9679e739b7ca1.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=69212@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 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.