unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Saku Laesvuori <saku@laesvuori.fi>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Contribute or create a channel?
Date: Sat, 2 Mar 2024 11:35:36 +0100	[thread overview]
Message-ID: <a1910c3d-47ed-353c-8dd4-38758d192bb1@crazy-compilers.com> (raw)
In-Reply-To: <k6sz2eph7wumutyfknnvxb7aro4x76njgl6mq54oo4s2exrvxt@b4r4pni6mhqk>

Am 01.03.24 um 19:16 schrieb Saku Laesvuori:
> It just requires a different updating method. The different versions can
> just be defined as separate packages (see postgresql for an example) and
> the user the defines which one they want to use. They can either refer
> to the package variable directly in scheme (e.g. postgresql-15) or on
> the command line with the name@version syntax (e.g. postgresql@15).

I'm aware of this way. It's fisable when there is a small number of 
packages like for postgres. But it is very laborious for rust packages 
already. I would not want to do the same for more than 200 packages.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



  reply	other threads:[~2024-03-02 10:36 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 [this message]
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
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=a1910c3d-47ed-353c-8dd4-38758d192bb1@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=saku@laesvuori.fi \
    /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).