unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: `guix package -u` upgrades packages to themselves
Date: Thu, 12 Apr 2018 01:37:30 -0700	[thread overview]
Message-ID: <87r2nkddmd.fsf@gmail.com> (raw)
In-Reply-To: <878t9unoat.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 11 Apr 2018 10:24:26 +0200")

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

Ricardo Wurmus <rekado@elephly.net> writes:

> That’s because the package version itself is insufficient.  In Guix
> we’re dealing with package “variants”.

Where is the concept of a package "variant" defined?  I briefly grepped
in the source but only found some ad-hoc stuff for Python and OCaml,
which actually do some kind of stuff with the package-properties.

> Guix will never upgrade a package to the same variant, but it can
> happen that there are different variants for the same version of a
> package.
>
> That’s usually because inputs to these packages have changed, which
> results in a new package output in the functional package management
> model.  The version stays the same, but since the inputs have changed,
> the output will be different and thus end up in a new directory.

How can the inputs have changed if Pierre is just running "guix package
-u" repeatedly?

-- 
Chris

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

  parent reply	other threads:[~2018-04-12  8:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  7:59 `guix package -u` upgrades packages to themselves Pierre Neidhardt
2018-04-11  8:24 ` Ricardo Wurmus
2018-04-11  9:40   ` Pierre Neidhardt
2018-04-11 12:24     ` Martin Castillo
2018-04-24  8:32     ` Ludovic Courtès
2018-04-12  8:37   ` Chris Marusich [this message]
2018-04-12  9:00     ` Ricardo Wurmus
2018-04-13  6:14       ` Chris Marusich
2018-04-13  6:19         ` 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=87r2nkddmd.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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.
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).