unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: wishlist: “repack” generations history of profile
Date: Sat, 04 Jun 2022 09:39:12 +0200	[thread overview]
Message-ID: <87fskknahr.fsf@xelera.eu> (raw)
In-Reply-To: <87k0a3aqh2.fsf@gmail.com>

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

Hi Simon,

I know you know very well all I'm saying here, I'm just commenting for
casual readers of this thread

zimoun <zimon.toutoune@gmail.com> writes:

[...]

> The generation #1 can be lost.  For sure it depends on the cluster
> policy but, as a sysadmin, I do not tell all the users that a GC will be
> run – and even if I am doing, I am sure that some user will miss to save
> the channels.scm and manifest.scm for each generation.

I don't know how easy or not is the implementation of this feature and
for sure it would be a plus, but IMHO all users must understand that for
their projects (profiles) to be reproducible and versioned the /only/
way is to keep channels.scm and manifests.scm in a VCS (i.e. git)

> That’s why, something like “repack” is missing.  As a user, I should be
> able to do
>
>     guix package --switch-generation=1
>
> whatever the sysadmin collects about the old generations and whatever I
> saved using some external tools.

...except you wish to reproduce the project on another machine, or
/gnu/store is lost or corrupted for some reason

Also consider that sometimes pepole in teams choose to work on the same
project in different (not shared) profiles (i.e. for reproducibility
testing), this way generation history is not the same and the only way
to "sync" would be to exchange channels.scm and manifest.scm

Also, from a collaborative workflow point of view, keeping the two
"reproduce me" files (channels and manifest) is more efficient since
people can describe what (and why) they chenged things between "saved"
project generations; not committed channels.scm and manifests.scm should
be considered "local testing"

IMVHO there is no easy workaround to keeping channels.scm and
manifests.scm in a VCS, better sooner than later users should do it

[...]

Happy hacking! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

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

  reply	other threads:[~2022-06-04  7:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 13:47 wishlist: “repack” generations history of profile zimoun
2022-05-21 11:30 ` Liliana Marie Prikler
2022-05-23 16:20   ` zimoun
2022-05-23 15:42 ` Ludovic Courtès
2022-05-23 16:58   ` zimoun
2022-05-30 15:40     ` Ludovic Courtès
2022-05-30 17:18       ` zimoun
2022-06-04  7:39         ` Giovanni Biscuolo [this message]
2022-06-05  9:45           ` zimoun
2022-06-05 11:16             ` Giovanni Biscuolo

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=87fskknahr.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).