Bug 15582

Summary:	allegro5, gaming library update to version 5 request
Product:	Mageia	Reporter:	Thewada <amorthewada>
Component:	New RPM package request	Assignee:	Rémi Verschelde <rverschelde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	lists.jjorge, marja11, mike.crecelius
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	allegro	CVE:
Status comment:

Description Thewada 2015-03-29 14:01:18 CEST

Allegro is a game programming library.
It's current version is 4.4.2 on Cauldron.
Could you please update it to version 5.0?
Thanks


Reproducible: 

Steps to Reproduce:

Comment 1 David Walser 2015-03-30 21:10:05 CEST

Such an update wouldn't be possible until Cauldron is branched after Mageia 5 is released.  Assigning to the maintainer.

Assignee: bugsquad => lists.jjorge

Mike Crecelius 2015-04-05 01:49:29 CEST

CC: (none) => mike.crecelius
Summary: allegro library update request => allegro, gaming library update to version 5 request
Source RPM: (none) => allegro

Comment 2 José Jorge 2015-10-25 12:25:22 CET

Not enough manpower for now, feel free to become a packager ;-)

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 3 Rémi Verschelde 2015-10-25 21:43:56 CET

I've actually packaged allegro5 for myself locally, so I'll probably import it in cauldron.

Status: RESOLVED => REOPENED
Resolution: WONTFIX => (none)
Assignee: lists.jjorge => bugsquad

Rémi Verschelde 2015-10-25 21:44:11 CET

Assignee: bugsquad => rverschelde

Comment 4 José Jorge 2015-10-25 21:58:40 CET

Nice, will it keep possible to install both? Some games never jumped from allegro4!

CC: (none) => lists.jjorge

Comment 5 Rémi Verschelde 2015-10-25 22:06:23 CET

Yes, allegro5 is actually a completely different library with a different lib name and headers, so it won't conflict with allegro4.

Marja Van Waes 2016-04-08 10:07:56 CEST

CC: (none) => marja11
Summary: allegro, gaming library update to version 5 request => allegro5, gaming library update to version 5 request

Comment 6 Rémi Verschelde 2017-03-12 23:17:48 CET

I copied our allegro (4) package to "allegro4", and updated the allegro package to 5.2.2. Now I need to fix the reverse dependencies to make them keep building against allegro4-devel, unless they have been ported.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED