Date: Tue, 25 May 2010 08:39:14 -0300 From: Jesse Smith <jessefrgsmith@yahoo.ca> To: Naram Qashat <cyberbotx@cyberbotx.com> Cc: freebsd-ports@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: ports/146920: Allegro runtime and Allegro-devel libraries incompatible Message-ID: <1274787554.2535.3.camel@hp-laptop> In-Reply-To: <4BFB3765.7030307@cyberbotx.com> References: <4BFB3765.7030307@cyberbotx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@cyberbotx.com> To: bug-followup@FreeBSD.org Cc: jessefrgsmith@yahoo.ca, freebsd-ports@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1274787554.2535.3.camel>