From: raingloom <raingloom@riseup.net>
To: Winter Hound <winterhound@yandex.ru>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Managing a multiple package definition
Date: Tue, 31 May 2022 15:52:07 +0200 [thread overview]
Message-ID: <20220531155207.0e1d60e0@riseup.net> (raw)
In-Reply-To: <817211653918941@mail.yandex.com>
On Mon, 30 May 2022 19:36:12 +0530
Winter Hound <winterhound@yandex.ru> wrote:
> Perhaps you may already know this
>
>
>
> ss
>
> ;; Defining a dummy package that is common to all
> I;; Taking fields that are common.
>
> Having multiple versions of the same package is convenient. Why
> isnt Guix has similar ? I know there inferior but having multiple
> versions in the same file would benefit right ?
My guess is it's because maintaining multiple version of a package is a
debugging and security nightmare. Fixing packages so that they can use
the latest version of a dependency is much more worthy of maintainer
efforts.
If you need to use a specific tag or commit so that you can compare
different versions of a package or something, package transformations
let you do that.
prev parent reply other threads:[~2022-05-31 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 14:06 Managing a multiple package definition Winter Hound
2022-05-31 13:52 ` raingloom [this message]
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=20220531155207.0e1d60e0@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=winterhound@yandex.ru \
/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.
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).