unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 64783@debbugs.gnu.org
Subject: bug#64783: Build of texlive-font-maps fails
Date: Wed, 09 Aug 2023 12:03:33 +0200	[thread overview]
Message-ID: <877cq4ih1p.fsf@web.de> (raw)
In-Reply-To: <877cqi1h8e.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]


Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>
>> Is there a package that says "all of texlive"? When working with LaTeX,
>> I do not know beforehand which packages I need but rather always need
>> all available to try out what works well.
>
> The "all of texlive" package is called `texlive'.
>
> When you have this one in your profile, you shouldn't need any
> "texlive-" prefixed package. OTOH, if you don't have `texlive', which is
> what I suggest, you need to start off with a base system, such as
> `texlive-scheme-basic' and extend it with TeX Live collections.

I found that after an update, pdflatex is broken with texlive and
additional packages, but works when 

Should all texlive-prefixed packages be removed from the manifest? If
yes: can we somehow add a warning about this?

I have this list in my manifest:

  "texlive"
  "texlive-ae"
  "texlive-amsfonts"
  "texlive-bin"
  "texlive-charter"
  "texlive-cm-super"
  "texlive-fontinst"
  "texlive-ec"
  "texlive-iwona"
  "texlive-latex-fonts"
  "texlive-rsfs"
  "texlive-inconsolata"
  "texlive-mdwtools"
  "texlive-ms"
  "texlive-polyglossia"
  "texlive-titlesec"
  "texlive-lh"
  "texlive-metafont"
  "texlive-mflogo"
  "texlive-mflogo-font"
  "texlive-palatino"
  "texlive-hyphen-complete"
  "texlive-times"
  "texlive-txfonts"
  "texlive-zapfding"


Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2023-08-09 11:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22  5:04 bug#64783: Build of texlive-font-maps fails Dr. Arne Babenhauserheide
2023-07-22 23:53 ` Nicolas Goaziou
2023-07-27  6:30   ` Dr. Arne Babenhauserheide
2023-07-29 22:32     ` Nicolas Goaziou
2023-08-09 10:03       ` Dr. Arne Babenhauserheide [this message]
2023-08-09 16:30         ` Nicolas Goaziou
2023-08-09 17:54           ` Dr. Arne Babenhauserheide
2023-07-23 14:24 ` Dominik Riva via Bug reports for GNU Guix
2023-07-24 13:08 ` Isaac van Bakel
2023-07-26  8:12   ` Josselin Poiret via Bug reports for GNU Guix
2023-07-26 14:34     ` Nicolas Goaziou
2023-08-08 19:53 ` bug#64783: biber not in $PATH with texlive only Julian Flake
2023-08-09 16:32   ` Nicolas Goaziou
2023-08-10  7:15     ` Julian Flake

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=877cq4ih1p.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=64783@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).