From: Attila Lendvai <attila@lendvai.name>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Mechanism for helping in multi-channels configuration
Date: Tue, 06 Feb 2024 17:16:38 +0000 [thread overview]
Message-ID: <7JIyQaT2Ww9Pes7QaxCq6t_7S_IHUSwTe4S3NN0hbjDcdebsmRn2TcITIw32cer2yh8SVoBvmUQUrYeILtay2FyCZA6YrHACinLdM-vgi_g=@lendvai.name> (raw)
In-Reply-To: <87v875kf5u.fsf@gmail.com>
> The wishlist is: provide a machine-readable description on guix-science
> channel side in order to help in finding the good overlap between
> commits of different channels.
i wrote about a missing abstraction here:
https://lists.gnu.org/archive/html/guix-devel/2023-12/msg00104.html
which is more or less related to this.
the git commit log is a too fine-grained granularity here. there should be something like a 'guix log' above the git log that could be used, among other things, to encode inter-channel dependencies.
maybe frequent semver releases for guix channels could work as reference points to be used to formally encode inter-channel dependencies? (and to guide the substitute chaching/building; mark "safe points" for the time-machine; etc)
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
Life is a tragedy to those who feel and a comedy to those who think.
next prev parent reply other threads:[~2024-02-06 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 10:36 Mechanism for helping in multi-channels configuration Simon Tournier
2024-02-03 15:27 ` Christina O'Donnell
2024-02-15 15:05 ` Simon Tournier
2024-03-18 16:05 ` Mechanism for helping in multi-channels configuration (and Xapian index) Christina O'Donnell
2024-05-06 12:05 ` Simon Tournier
2024-02-06 14:18 ` Mechanism for helping in multi-channels configuration Maxim Cournoyer
2024-02-06 17:08 ` Attila Lendvai
2024-02-06 17:16 ` Attila Lendvai [this message]
2024-02-15 21:14 ` Simon Tournier
2024-03-12 12:44 ` Attila Lendvai
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='7JIyQaT2Ww9Pes7QaxCq6t_7S_IHUSwTe4S3NN0hbjDcdebsmRn2TcITIw32cer2yh8SVoBvmUQUrYeILtay2FyCZA6YrHACinLdM-vgi_g=@lendvai.name' \
--to=attila@lendvai.name \
--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).