From: Dan Partelly <dan_partelly@rdsor.ro>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Ensuring we don't break user systems
Date: Sun, 29 Jul 2018 19:58:07 +0300 [thread overview]
Message-ID: <2B63200B-FEE2-4FC4-9A0D-371732E5D700@rdsor.ro> (raw)
In-Reply-To: <871sbmpe7y.fsf@gmail.com>
Even more important than this, is that the users do not end up with a broken package manager following a guix pull. Which is what happened pretty often in my experiences with GuixSD. Yes, yes, you can “roll-back”. The bottom line is , the system should not break in the first place. GuixSD should not inflict its development branch of the package manager on the world, and the stable branch should be regression tested
> On Jul 29, 2018, at 12:45, Pierre Neidhardt <ambrevar@gmail.com> wrote:
>
> I like this a lot!
>
> Security aside, I also think it's very important for 1.0 that casual users
> (i.e. non-devs) can `guix pull' without rebuilding half their packages because hydra
> hadn't had the time to rebuild everything from the latest commit.
>
> --
> Pierre Neidhardt
next prev parent reply other threads:[~2018-07-29 16:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 9:40 Ensuring we don't break user systems Julien Lepiller
2018-07-29 9:45 ` Pierre Neidhardt
2018-07-29 16:58 ` Dan Partelly [this message]
2018-07-29 16:51 ` Dan Partelly
2018-07-29 17:28 ` Christopher Baines
2018-07-29 17:59 ` Dan Partelly
2018-07-30 21:16 ` Nils Gillmann
2018-07-30 21:24 ` Amirouche Boubekki
2018-07-30 21:30 ` Nils Gillmann
2018-07-31 6:17 ` Dan Partelly
2018-07-31 7:45 ` Julien Lepiller
2018-07-29 17:51 ` Julien Lepiller
2018-07-29 18:07 ` Dan Partelly
2018-07-29 23:41 ` Ludovic Courtès
2018-07-30 6:33 ` Dan Partelly
2018-07-30 10:58 ` Hartmut Goebel
2018-07-31 12:40 ` Pjotr Prins
2018-07-31 13:15 ` Clément Lassieur
2018-07-31 13:18 ` Julien Lepiller
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=2B63200B-FEE2-4FC4-9A0D-371732E5D700@rdsor.ro \
--to=dan_partelly@rdsor.ro \
--cc=ambrevar@gmail.com \
--cc=guix-devel@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 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.