ports/146920: Allegro runtime and Allegro-devel libraries incompatible

[Jesse Smith]

The following reply was made to PR ports/146920; it has been noted by GNATS.

From: Jesse Smith <jessefrgsmith at yahoo.ca>
To: Naram Qashat <cyberbotx at cyberbotx.com>
Cc: bug-followup at FreeBSD.org, freebsd-ports at FreeBSD.org
Subject: Re: ports/146920: Allegro runtime and Allegro-devel libraries
 incompatible
Date: Tue, 25 May 2010 08:39:14 -0300

 Naram,
 
 Thank you for your quick reply. I think that clears things up for me.
 The issue I had run into was my code was written to work with Allegro
 4.2 and I found 4.3 was missing a function I was using. However,
 following your advice, I've made some changes and my package is
 compiling again.
 
 Jesse
  
 
 -----Original Message-----
 From: Naram Qashat <cyberbotx at cyberbotx.com>
 To: bug-followup at FreeBSD.org
 Cc: jessefrgsmith at yahoo.ca, freebsd-ports at FreeBSD.org
 Subject: Re: ports/146920: Allegro runtime and Allegro-devel libraries
 incompatible
 Date: Mon, 24 May 2010 22:35:17 -0400
 
 As the current maintainer of the Allegro ports, I can tell you a few things 
 here.  For one, the devel/allegro port will be updated to 4.4.1.1 as soon as I 
 can get some more time to finish patching it for FreeBSD and making sure those 
 patches work.  For two, devel/allegro-devel is meant to be Allegro's 
 developmental version and does not necessarily need to be compatible with 
 devel/allegro in any way, and as such, once I get devel/allegro updated, I will 
 be updating devel/allegro-devel to 4.9.19.  So basically, I would say is it up 
 to the maintainers of ports relying on any Allegro ports to side with one of the 
 ports and not rely on the other port.  I can't force them into doing so, however.
 
 Thanks,
 Naram Qashat