From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: Rollback problems
Date: Thu, 24 Jan 2013 00:17:54 +0100 [thread overview]
Message-ID: <201301240017.55013.andreas@enge.fr> (raw)
In-Reply-To: <87mwvzsdzt.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1879 bytes --]
Am Mittwoch, 23. Januar 2013 schrieb Ludovic Courtès:
> And what if you roll back once you’re at the empty profile?
Then nothing should happen.
> It seems more intuitive for me to error out like this, because there was
> really nothing but nothingness before “hello” was installed. :-)
> WDYT?
No, I disagree; when I have nothing, install hello and roll back, I should
be back to nothing. Some other opinions would be useful on this matter.
> This is expected (same behavior as nix-env.) Profile generations are
> not deleted unless you explicitly do so; this is what guarantees that
> one can roll back anywhere they want.
>
> But I wonder if this is really worth the trouble. In my experience, a
> scenario like the one above rarely happens, if ever.
I find the behaviour of roll back currently very confusing, and the
situation looks reasonable to me:
I install hello, it works, so I keep it.
I install freetype, it does not work, so I drop it again.
I install file, it does not work, so I drop it again.
Now I expect to have only hello, but I have hello and freetype.
Of course, instead of rolling back, I can also uninstall. But the same
situation occurs when one replaces the package names by different versions,
I suppose.
I see installing packages and rolling back as steps forward and backward.
Going into direction B and back, then going into direction C and back
should not leave me with one step forward in direction B.
Note that I did not use nix before; so I am just arguing from what would
intuitively be the correct behaviour of --roll-back for me: Being in
situation A, doing something to bring me into situation B and rolling back
should put me into situation A again, not something that resembles
situation A, but with memories of B.
Again, some other opinions would be useful.
Andreas
[-- Attachment #2: Type: text/html, Size: 7170 bytes --]
next prev parent reply other threads:[~2013-01-23 23:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 20:48 Rollback problems Andreas Enge
2013-01-23 22:58 ` Ludovic Courtès
2013-01-23 23:17 ` Andreas Enge [this message]
2013-01-24 11:34 ` Ludovic Courtès
2013-01-24 15:33 ` Alex Sassmannshausen
2013-01-24 15:59 ` Ludovic Courtès
2013-01-24 20:52 ` Ludovic Courtès
2013-01-25 2:44 ` Nikita Karetnikov
2013-01-25 13:54 ` Alex Sassmannshausen
2013-01-25 14:48 ` Andreas Enge
2013-01-25 14:53 ` Ludovic Courtès
2013-01-27 17:05 ` Ludovic Courtès
2013-01-28 22:10 ` Andreas Enge
2013-01-28 22:44 ` Ludovic Courtès
2013-01-25 3:08 ` Nikita Karetnikov
2013-01-27 17:06 ` Ludovic Courtès
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=201301240017.55013.andreas@enge.fr \
--to=andreas@enge.fr \
--cc=bug-guix@gnu.org \
--cc=ludo@gnu.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).