unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 33285@debbugs.gnu.org
Subject: bug#33285: Installing, then removing, a package yields a different profile
Date: Fri, 08 Feb 2019 19:44:33 -0800	[thread overview]
Message-ID: <87a7j5sk0u.fsf@gmail.com> (raw)
In-Reply-To: <87mun7onte.fsf@fsfe.org> (Jelle Licht's message of "Thu, 07 Feb 2019 12:11:41 +0100")

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

Jelle Licht <jlicht@fsfe.org> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> [snip]
>>
>> I think it’s fine to leave it as it is, then.  “--install” and
>> “--remove” are stateful and should be expected to have quirks like this.
>> (E.g. upgrading Guix in between two “--install”s can lead to
>> a mosaic of a profile that could not be produced any other way.)
>
> This seems like a very reasonable perspective on this issue, so I
> concur. Should we state this explicitly somewhere in the manual?

Thinking about it that way, I agree it makes sense as is.  I think it's
valid to say this isn't a bug, then.  I've confirmed that "adding" and
then "removing" a package by using a stateless method (e.g., the "guix
package -m" method) results in the expected behavior: the first and
third profile generations refer to exactly the same profile:

--8<---------------cut here---------------start------------->8---
$ ls -al /tmp/test-profile*
lrwxrwxrwx 1 marusich users 19 Feb  8 19:39 /tmp/test-profile -> test-profile-3-link
lrwxrwxrwx 1 marusich users 51 Feb  8 19:39 /tmp/test-profile-1-link -> /gnu/store/7j6gy2xvyz7zzpccwsssbxxzykv6q0zg-profile
lrwxrwxrwx 1 marusich users 51 Feb  8 19:39 /tmp/test-profile-2-link -> /gnu/store/yz9qskdl926mdy1i63yzsqwhcciswv90-profile
lrwxrwxrwx 1 marusich users 51 Feb  8 19:39 /tmp/test-profile-3-link -> /gnu/store/7j6gy2xvyz7zzpccwsssbxxzykv6q0zg-profile
--8<---------------cut here---------------end--------------->8---

I'm satisfied.  I'm honestly not sure it's worth mentioning in the
manual.  I feel like explaining it would add little value and just
clutter up the documentation.  This was mainly a curiosity for me.

-- 
Chris

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

  reply	other threads:[~2019-02-09  3:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06  6:25 bug#33285: Installing, then removing, a package yields a different profile Chris Marusich
2018-11-06 14:25 ` Ludovic Courtès
2018-11-07  7:08   ` Chris Marusich
2019-02-03 23:14     ` Ricardo Wurmus
2019-02-04 18:02       ` Ludovic Courtès
2019-02-06 13:19         ` Ludovic Courtès
2019-02-06 14:29           ` Ricardo Wurmus
2019-02-07 11:11             ` Jelle Licht
2019-02-09  3:44               ` Chris Marusich [this message]
2019-03-12 11:58                 ` 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

  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=87a7j5sk0u.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=33285@debbugs.gnu.org \
    --cc=jlicht@fsfe.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 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).