unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Contribute or create a channel?
Date: Sat, 2 Mar 2024 11:32:37 +0100	[thread overview]
Message-ID: <1d7c3eeb-0ca0-d29e-53ae-77eb1f2d66e5@crazy-compilers.com> (raw)
In-Reply-To: <87y1b1shfm.fsf@elephly.net>

Hi Ricardo,
> I think it would be preferable to have one LTS version in Guix.
Okay, that's a clear statement.

> whether to grant you commit rights to handle these upgrades
> by yourself.

Well, I already have commit rights :-) Anyhow the review period is a bit 
hindering, esp. for bug-fixes.


>> OTOH in Guix, maintaining several version seems laborious.
> What makes you say this?  What exactly is the obstacle here?

The only way I know for handling several versions of the same package is 
what Saku Laesvuori described: Adding a new variable for each of these 
versions, possibly making the older version inherit from the new one. 
This means moving quite some code on every new version. Done this for 
quite some rust-packages and it i quite laborious and hard to automate. 
And for Tryton we have about 200 packages and growing.

When using branches (in a channel) one would just checkout that branch, 
automatically apply the patches and commit. If the version is no longer 
supported, simply stop applying updates on that branch.

Maybe using one file per release (and accept duplicate code) would be a 
suitable workaround.

-- 
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:33 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
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 [this message]
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=1d7c3eeb-0ca0-d29e-53ae-77eb1f2d66e5@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --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).