[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/2] gnu: Add allegro-5.0.
From: |
Ricardo Wurmus |
Subject: |
Re: [PATCH 2/2] gnu: Add allegro-5.0. |
Date: |
Wed, 20 Jul 2016 07:52:44 +0200 |
User-agent: |
mu4e 0.9.16; emacs 24.5.1 |
Thompson, David <address@hidden> writes:
> On Tue, Jul 19, 2016 at 4:57 PM, Ricardo Wurmus <address@hidden> wrote:
>> * gnu/packages/game-development.scm (allegro-5.0): New variable.
>
> I assume you have a use-case that calls for keeping multiple versions
> of Allegro 5 around? Looks fine to me, if so.
Allegro 5.2 merges the unstable with the stable branch. It breaks API
and requires applications to define “ALLEGRO_UNSTABLE” to use unstable
features.
Allegro 5.0.11 is the last of the stable releases and the last to use
the pkg-config identifier “allegro-5.0”, which some applications look
for.
I’m not sure if this is enough to justify keeping 5.0 or if we should
patch the configure scripts of applications that look for “allegro-5.0”.
~~ Ricardo
- [PATCH 1/2] gnu: Add allegro., Ricardo Wurmus, 2016/07/19
- Re: [PATCH 1/2] gnu: Add allegro., Thompson, David, 2016/07/19
- Re: [PATCH 1/2] gnu: Add allegro., Ricardo Wurmus, 2016/07/20
- Package API compatibility and guix package variable names, Danny Milosavljevic, 2016/07/27
- Re: Package API compatibility and guix package variable names, Andreas Enge, 2016/07/27
- Re: Package API compatibility and guix package variable names, Danny Milosavljevic, 2016/07/27
- Re: Package API compatibility and guix package variable names, Andreas Enge, 2016/07/27
- Re: Package API compatibility and guix package variable names, Chris Marusich, 2016/07/28