all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "jgart" <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: guix refresh --update Removes Needed Dependencies
Date: Wed, 22 Nov 2023 22:45:48 +0100	[thread overview]
Message-ID: <8734wxihrn.fsf@gnu.org> (raw)
In-Reply-To: <e46e2e02ebbeb9d743913a446f72e5a1@dismail.de> (jgart@dismail.de's message of "Sat, 18 Nov 2023 01:59:51 +0000")

Hi jgart,

"jgart" <jgart@dismail.de> skribis:

> ./pre-inst-env guix refresh --update python-sphinx

[...]

> -           ;; The Sphinx LaTeX library '\RequirePackage' or \\usepackage
> -           ;; these:
> -           texlive-amsfonts             ;amsmath, amssymb, amstext
> -           texlive-amsmath
> -           texlive-capt-of
> -           texlive-carlisle             ;remreset

To avoid this problem one can add package properties such as
‘updater-extra-native-inputs’ in this case:

  https://guix.gnu.org/manual/devel/en/html_node/Invoking-guix-refresh.html#index-updater_002dextra_002dinputs_002c-package-property

However, the way it’s implemented right now, you have to list the name
of every input that should be preserved by ‘guix refresh -u’, which is
inconvenient in this particular case because there are many of them.

I can think of two ways to improve on that:

  1. Use one of the ‘texlive-scheme-*’ packages instead of this long
     list.  :-)

  2. Change the code to interpret extra inputs are regexps instead of
     names.

Thoughts?

Ludo’.


  parent reply	other threads:[~2023-11-22 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18  1:59 guix refresh --update Removes Needed Dependencies jgart
2023-11-22  9:47 ` Csepp
2023-11-22 21:45 ` Ludovic Courtès [this message]
2023-11-23  7:08   ` Efraim Flashner
2024-02-10 12:09 ` Ricardo Wurmus

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=8734wxihrn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    /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.