[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Package API compatibility and guix package variable names

From: Andreas Enge
Subject: Re: Package API compatibility and guix package variable names
Date: Wed, 27 Jul 2016 18:19:18 +0200
User-agent: Mutt/1.6.1 (2016-04-27)

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]