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

Re: Recommencement of Allegro packaging (in the Debian Games Team)

On Sun, Apr 1, 2012 at 2:29 AM, Tobias Hansen wrote:

> After my ITP for Allegro 5, Andreas Rönnquist has volunteered to join me
> maintaining Allegro, and we decided to also take care of Allegro 4,
> which is orphaned and needs to be updated from 4.2 to 4.4.

Thanks for your work.

>  alex4

If anyone wants to work on porting alex4, I can give you upstream commit access.

> Allegro 4 and 5 are incompatible, so we need both in the archive.


> Since future Allegro transitions could become a bit involved, I would
> like to make sure that we choose the most convenient package names. I
> would call the Allegro 5.0 source package allegro5 in the hope that we
> won't need a new one for Allegro 5.2 etc. The library packages have to
> be called liballegro5.0 after the soname. What about the dev packages?
> liballegro5-dev or liballegro5.0-dev providing liballegro5-dev? For the
> documentation I was thinking allegro5-doc.

Are the APIs also incompatible between 4 and 5?

> Currently the allegro4.2 source package builds among others the packages
> allegro-examples and allegro-demo. The sources are in the liballegro-doc
> package. I don't think allegro-examples or allegro-demo are very
> interesting or important, so I suggest discontinuing them. We will
> continue to ship the sources of the examples in the doc packages. Should
> we still continue to build the examples (without packaging the results)
> to make sure that they build successfully?

Sounds good.



Reply to: