From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Attila Lendvai <attila@lendvai.name>
Cc: Ricardo Wurmus <rekado@elephly.net>,
Hartmut Goebel <h.goebel@crazy-compilers.com>,
guix-devel@gnu.org
Subject: Re: Contribute or create a channel?
Date: Wed, 13 Mar 2024 09:43:05 +1100 [thread overview]
Message-ID: <871q8ful52.fsf@zancanaro.id.au> (raw)
In-Reply-To: <Ct4d938WdY9_6nUuwKJD6nd_l8s4fWfNJbq-phdYoAOmUz3PclVDb3aPFCfD1Be8ATonlJNdRO9pw6-k8UR2blIU_a33eqRFA0OVokkdzi0=@lendvai.name> (Attila Lendvai's message of "Tue, 12 Mar 2024 13:18:21 +0000")
On Tue, Mar 12 2024, Attila Lendvai wrote:
> channels are a step towards this, but they are not enough in their
> current form to successfully accommodate for such a setup. an obvious
> thing that is missing is a way to formally express inter-channel
> dependencies, including some form of versioning.
Do we not have this? The manual documents a mechanism for channel
dependencies in "(guix) Declaring Channel Dependencies".
I haven't used it, but it looks like the dependencies are declared as
channels, which can have the usual branch/commit specifications to tie
them to specific versions.
What are we missing?
Carlo
next prev parent reply other threads:[~2024-03-12 22:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 16:36 Contribute or create a channel? Hartmut Goebel
2024-03-01 18:16 ` Saku Laesvuori
2024-03-02 10:35 ` Hartmut Goebel
2024-03-01 21:13 ` Attila Lendvai
2024-03-01 22:35 ` Ricardo Wurmus
2024-03-12 13:18 ` Attila Lendvai
2024-03-12 16:56 ` Troy Figiel
2024-03-12 22:43 ` Carlo Zancanaro [this message]
2024-03-13 12:35 ` Attila Lendvai
2024-03-14 18:06 ` Josselin Poiret
2024-03-01 22:39 ` Ricardo Wurmus
2024-03-02 10:32 ` Hartmut Goebel
2024-03-04 8:32 ` Andreas Enge
2024-03-05 14:19 ` Hartmut Goebel
2024-03-05 22:34 ` 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=871q8ful52.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=rekado@elephly.net \
/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).