From: Ricardo Wurmus <rekado@elephly.net>
To: "Sławomir Lach" <slawek@lach.art.pl>
Cc: guix-devel@gnu.org
Subject: Re: The way to promote GUIX package manager
Date: Wed, 26 Jan 2022 22:38:33 +0100 [thread overview]
Message-ID: <878rv2jhqn.fsf@elephly.net> (raw)
In-Reply-To: <3101606.jC9oV0cg2h@localhost.localdomain>
Sławomir Lach <slawek@lach.art.pl> writes:
> Solution is simple:
> 1. Keep older packages in GUIX repo, so developers could request older version
> in scripts
Unforunately, it’s really not that simply to keep older packages around.
I’m maintaining packages for a bunch of bioinformatics tools, for
example, which are stuck in the past. Building them becomes more and
more difficult as time passes and the rest of the world moves on. It is
not feasible to maintain an ever-growing collection of outdated software
and their toolchains.
But: Guix supports channels, so people who absolutely must use GCC 3 to
build their abandoned tools to build their old source code that’s stuck
in the past can totally do that.
> Minus: possible security hell.
:)
--
Ricardo
next prev parent reply other threads:[~2022-01-26 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 11:09 The way to promote GUIX package manager Sławomir Lach
2022-01-26 21:38 ` Ricardo Wurmus [this message]
2022-01-26 22:40 ` Yasuaki Kudo
2022-01-26 22:42 ` Ricardo Wurmus
2022-01-26 23:15 ` Yasuaki Kudo
2022-01-27 23:35 ` Bengt Richter
2022-01-27 23:55 ` Yasuaki Kudo
2022-01-28 1:43 ` David Pirotte
2022-01-28 14:48 ` Bengt Richter
2022-01-26 23:38 ` Vagrant Cascadian
2022-02-05 13:54 ` Ludovic Courtès
2022-02-05 20:39 ` Ricardo Wurmus
2022-02-06 18:54 ` Vagrant Cascadian
2022-02-06 19:19 ` Ricardo Wurmus
2022-02-14 17:23 ` Ludovic Courtès
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=878rv2jhqn.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=slawek@lach.art.pl \
/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).