From: Andreas Enge <andreas@enge.fr>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Package API compatibility and guix package variable names
Date: Wed, 27 Jul 2016 18:19:18 +0200 [thread overview]
Message-ID: <20160727161918.GA5300@solar> (raw)
In-Reply-To: <20160727175431.35fc6326@scratchpost.org>
On Wed, Jul 27, 2016 at 05:54:31PM +0200, Danny Milosavljevic wrote:
> In my humble opinion it would best if there was an "allego-5.0" and an "allegro" variable, with the "allegro" variable not being referenced by any other package (they would reference "allegro-5.0" instead - or whatever major API version they need, for example "allegro-5.2").
> If something becomes incompatible, its name should change.
It is our common practice to not re-encode the version into the name: Usually
the unnumbered name simply stands for the latest version, Only when we need to
keep several versions around do we add a versioned name for the earlier one.
In this way, updating dependencies becomes easier: Most of the time, a later
version of a dependency will work. To follow your suggestion, we would
ultimately add the soname of libraries to package names, and then whenever
some package is updated, all packages depending on it would need to have
their inputs rewritten. This would not be very practical.
Andreas
next prev parent reply other threads:[~2016-07-27 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 20:57 [PATCH 1/2] gnu: Add allegro Ricardo Wurmus
2016-07-19 20:57 ` [PATCH 2/2] gnu: Add allegro-5.0 Ricardo Wurmus
2016-07-20 1:39 ` Thompson, David
2016-07-20 5:52 ` Ricardo Wurmus
2016-07-20 13:03 ` Thompson, David
2016-07-20 1:37 ` [PATCH 1/2] gnu: Add allegro Thompson, David
2016-07-20 19:54 ` Ricardo Wurmus
2016-07-27 15:54 ` Package API compatibility and guix package variable names Danny Milosavljevic
2016-07-27 16:19 ` Andreas Enge [this message]
2016-07-27 21:06 ` Danny Milosavljevic
2016-07-27 21:33 ` Andreas Enge
2016-07-28 6:04 ` Chris Marusich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160727161918.GA5300@solar \
--to=andreas@enge.fr \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.