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

Re: would somebody be interested in updating liballegro from 5.0 to 5.2 ?

On 2016-04-20 18:58, shirish शिरीष wrote:
On 20/04/2016, James Cowgill <jcowgill@debian.org> wrote:
On Wed, 2016-04-20 at 16:03 +0000, shirish शिरीष wrote:
I also did a mock purge to see if there were any libraries which were
affected and the only one which seems to be affected is libdumb1-dev
I am guessing the only reason why this version is not being shipped
due to the dumb library allegro 4 support issue, see #799008 as well
as the relevant issue in libdumb's new upstream

libdumb is built against allegro4. How will upgrading allegro5 from 5.0
to 5.2 have any effect here?

Is this a correct assessment of the situation. Is there a possibility
of having liballegro5.2 and the relevant libdumb version have it in
experimental so people who want to try some games with the new
  can try it ?  See
http://forum.freegamedev.net/viewtopic.php?f=22&t=6477 for discussion
of a game which uses the newer version of a library.

I don't see why allegro 5.2 can't be uploaded at some point. What do
you need libdumb for? The thread doesn't mention anything about it.

For some reason when I try to purge allegro5.0 libdumb1-dev also get
purged so thought it was part of the liballegro5.0 package, see if I
am doing something wrong.

[$] sudo aptitude purge liballegro5.0 liballegro5-dev
liballegro-ttf5.0 liballegro-ttf5-dev liballegro-physfs5.0
liballegro-physfs5-dev liballegro-image5.0 liballegro-image5-dev
liballegro-dialog5.0 liballegro-dialog5-dev liballegro-audio5.0
liballegro-audio5-dev liballegro-acodec5.0 liballegro-acodec5-dev
[sudo] password for shirish:
The following packages will be REMOVED:
   liballegro-acodec5-dev{pu} liballegro-acodec5.0{pu}
liballegro-audio5-dev{pu} liballegro-audio5.0{pu}
liballegro-dialog5-dev{pu} liballegro-dialog5.0{pu}
liballegro-image5-dev{pu} liballegro-image5.0{pu}
liballegro-physfs5-dev{pu} liballegro-physfs5.0{pu}
liballegro-ttf5-dev{pu} liballegro-ttf5.0{pu} liballegro5-dev{p}
liballegro5.0{p} libdumb1-dev{u}
0 packages upgraded, 0 newly installed, 15 to remove and 2 not upgraded.
Need to get 0 B of archives. After unpacking 3,508 kB will be freed.
Do you want to continue? [Y/n/?] n

As can be seen if I purge liballegro5.0 and the relevant packages then
libdumb1-dev also gets purged.

Also -

[$] aptitude why libdumb1-dev

i   liballegro5-dev        Recommends liballegro-acodec5-dev
i A liballegro-acodec5-dev Depends  libdumb1-dev

I do not think that the DUMB-issue is relevant here. Sure it would be nice to have a recent version in Debian, but not having it does not block 5.2 as it will (hopefully/likely) link fine with the old DUMB 0.9.3 in Debian. Allegro5 integrates DUMB and thus depends on it. For Allegro4 DUMB itself shipped code integrating it into Allegro4.

During the forking process of DUMB, this Allegro4-support got lost. [1] I tried to bring it back but got stuck at the same issue that Github-user winterheart came across when he tried. [2]

Anyways, the original version is quite old and the fork has received many bugfixes in the meantime. So it would indeed be nice to bring the new DUMB in.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799008
[2] https://github.com/kode54/dumb/issues/21#issuecomment-193189274

Reply to: