all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thiago Jung Bauermann via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 49472-done@debbugs.gnu.org
Subject: [bug#49472] [PATCH core-updates] gnu: texlive-bin: Use ‘--with-banner-add’ configure option
Date: Sat, 24 Jul 2021 19:21:38 -0300	[thread overview]
Message-ID: <8483354.X44IXdQGTD@popigai> (raw)
In-Reply-To: <87sg03aj9t.fsf@gnu.org>

Hello,

Em sábado, 24 de julho de 2021, às 11:17:18 -03, Ludovic Courtès escreveu:
> Hi,
> 
> Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:
> > The “Building TeX Live” manual has a section about configure options
> > for
> > 
> > distro builds¹. They mention this option:
> >     --with-banner-add=/SomeDistro
> >     
> >     This isn’t technically required, but is strongly recommended, so
> >     your
> >     build and your distro can be distinguished from others.
> > 
> > Therefore add it to texlive-bin. This is how it appears on LuaTeX, for
> > 
> > example (it also shows up in other engines’ banners):
> >     $ luatex
> >     This is LuaTeX, Version 1.13.0 (TeX Live 2021/GNU Guix)
> >     restricted system commands enabled.
> >     **
> > 
> > The other options mentioned in that section are already being used.
> > 
> > ¹ http://www.tug.org/texlive/doc/tlbuild.html#Distro-builds
> > 
> > * gnu/packages/tex.scm (texlive-bin)[arguments]: Add
> > ‘--with-banner-add’
> > option.
> 
> Applied, thanks!

Thank you!

I appreciate your attention even to minor patches such as this one.

-- 
Thanks,
Thiago






      reply	other threads:[~2021-07-24 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08 22:13 [bug#49472] [PATCH core-updates] gnu: texlive-bin: Use ‘--with-banner-add’ configure option Thiago Jung Bauermann via Guix-patches via
2021-07-24 14:17 ` bug#49472: " Ludovic Courtès
2021-07-24 22:21   ` Thiago Jung Bauermann via Guix-patches via [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8483354.X44IXdQGTD@popigai \
    --to=guix-patches@gnu.org \
    --cc=49472-done@debbugs.gnu.org \
    --cc=bauermann@kolabnow.com \
    --cc=ludo@gnu.org \
    /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.