From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 31142@debbugs.gnu.org
Subject: bug#31142: guix package --upgrade reverses the order of packages
Date: Thu, 28 Mar 2019 15:10:39 +0100 [thread overview]
Message-ID: <87a7hfay3k.fsf@gnu.org> (raw)
In-Reply-To: <87d0mbnm0f.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 28 Mar 2019 14:53:20 +0100")
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> At first sight, to me, it’s not entirely clear how to determine whether
>> something is to be upgraded in the presence of propagated inputs.
>
> I think the linked discussion suggested we checked upgrades
> recursively. Wouldn't that work?
Maybe! Let’s open a new bug. :)
>> And more importantly, I think the “imperative” model is necessarily not
>> as expressive and “clean” as ‘--manifest’. There are tradeoffs to make.
>
> Sorry, I don't understand what you mean. How do we upgrade
> declaratively?
Just ‘guix pull && guix package --manifest=my-stuff.scm’.
Ludo’.
next prev parent reply other threads:[~2019-03-28 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 5:57 bug#31142: guix package --upgrade reverses the order of packages Chris Marusich
2018-04-18 21:15 ` Ludovic Courtès
2019-01-15 11:07 ` Ludovic Courtès
2019-03-27 11:33 ` Pierre Neidhardt
2019-03-28 12:49 ` Ludovic Courtès
2019-03-28 12:56 ` Pierre Neidhardt
2019-03-28 13:30 ` Ludovic Courtès
2019-03-28 13:53 ` Pierre Neidhardt
2019-03-28 14:10 ` Ludovic Courtès [this message]
2019-03-28 13:01 ` Maxim Cournoyer
2019-03-28 13:13 ` Pierre Neidhardt
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=87a7hfay3k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31142@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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).