Thomas Frohwein writes: > Please find a tarball of sdl12-compat in the attachment. This is the > upstream-endorsed way of running SDL-1.2 applications at this point, > since SDL 1.2 has been end-of-life for a while and isn't receiving > updates anymore. It reimplements SDL 1.2 on top of SDL2. > > It is supposed to be a full replacement of devel/sdl. ... > To build sdl12-compat, devel/sdl needs to be uninstalled because of the > conflict in library and header files. To build consumers, if they > depend on devel/sdl directly, this needs to be adjusted to > devel/sdl12-compat. > > If I get an ok, would need to update the consumer for the different > dependency, and retire devel/sdl with quirks entry. This feels complicated. Why not just replace devel/sdl with this? The library it provides is named the same, it's intended to be a drop-in replacement, the ports themselves need to be tested but will probably be fine. We won't have to deal with quirks or @conflict markers. Ports that fail to build can be marked broken. As you pointed out, most ports using SDL 1.2 are leaf ports and most of them are pretty old, and most of them work with this anyway, so any breakage will be minor and easily fixed.
No comments:
Post a Comment