all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 2/2] gnu: Add allegro-5.0.
Date: Wed, 20 Jul 2016 07:52:44 +0200	[thread overview]
Message-ID: <87vb00zwib.fsf@elephly.net> (raw)
In-Reply-To: <CAJ=RwfY3S_KpaKsZqk-WCTo2cbfpFrMvjfEPtMQpLcbxAt16gg@mail.gmail.com>


Thompson, David <dthompson2@worcester.edu> writes:

> On Tue, Jul 19, 2016 at 4:57 PM, Ricardo Wurmus <rekado@elephly.net> 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

  reply	other threads:[~2016-07-20  5:52 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 [this message]
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
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=87vb00zwib.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=dthompson2@worcester.edu \
    --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.