allegro5

[ryandesign (Ryan Carsten Schmidt)]

The allegro port is at version 4.4.2. Allegro 5.0.4 is available. Allegro 5 has been in development since 2002, so I imagine it breaks the API. Should we make a new port allegro5 for this?

[raimue (Rainer Müller)]

Yes, allegro 5.x introduces a new, incompatible API. But so far I have not encountered any game/software I wanted to use that required allegro 5.x.

There seem to be only three ports depending on allegro at the moment:

$ port echo depends:allegro
atanks                          
liquidwar                       
swig-allegro

Should we move allegro to allegro4 (with replaced_by) and create a new allegro5? We could also do the same for swig-allegro by creating swig-allegro4 and swig-allegro5.

[ryandesign (Ryan Carsten Schmidt)]

I was trying to update ship24 to version 1.4.1 and it seems to want allegro5 -- if indeed it still works on Mac at all anymore; the web site says it requires Windows but I figured I'd give it a try.

If we can just make an allegro5 port that would be plenty for now. We can worry about renaming allegro to allegro4 later. But you're right that's probably a good idea eventually.

[icaines77@…]

Cc Me!

[icaines77@…]

Portfile for allegro5

[icaines77@…]

Changes from the current allegro portfile.

[raimue (Rainer Müller)]

allegro5 with changes committed in r94100, allegro marked as conflicting in r94102.