packaging a closedsource game

[Manuel A. Fernandez Montecelo]

2016-11-14 11:02 GMT+01:00 jsaak <jsaak at napalm.hu>:
> Hi Manuel,
>
> Thank you for your answer!
>
> I fear that this solution is not the best for me.
> 7kaa is opensource and included in the debian distro.
> I can not do either of these.
>
> What I wanted to do is put a mygame.deb on a website. And try to make it as
> easy as possible to install it.
>
> Since you decided to include SONAME/SOVERSION to the package name, whenever
> that change i will have to regenerate my .deb file, and keep multiple
> versions alive.
>
> Maybe a virtual package or a dependency package would help me named libsdl2
> which depends on the current libsdl2. Just like libboost-dev.

Well, that's the idea of using "libsdl2-dev", "libsdl2-net-dev" as
build dependencies etc and then the ${shlib:Depends} instead of
hardcoding libsdl2-2.0-0 -- kind of works like libboost-dev.  The
mechanism of creating packages chooses the name of "libsdl2-2.0-0" or
another one if it changes.  The boost packages change all the time, at
least once every year, so even if libboost-dev doesn't change it will
not work for you -- libboost-thread1.58 jumps to libboost-thread1.61
and so on very often.

I don't see why you cannot use this option even if your game is not
free software/open source, or not present in Debian -- unless you
don't use the Debian tools at all to create it.

The libsdl1.2-dev ones are there for about 15 years now, and the
libsdl2-dev also for 4 years if not more, and I am sure that it will
be there for many years in the future.

In practice, the libsdl2-2.0-0 did not change in 4 years either,
although it will change at least as often as the -dev one.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>