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

Re: supertuxkart 0.7.3



On 12/10/2012 11:52 AM, Vincent Cheng wrote:
On Mon, Dec 10, 2012 at 2:25 AM, Paul Wise<pabs@debian.org>  wrote:
Beg upstream to be reasonable and push their patches upstream.
This is what auria (one of stk's devs) said (in one of the bug reports
I linked earlier, i.e. [1]): "irrlicht is configured through a header,
and the irrlicht developers specifically told us to configure irrlicht
in our builds because they wouldn't change the defaults for everyone.
The logical conclusion is that since STK doesn't use the default
irrlicht configuration it must use its own irrlicht. So at this point
Linux distributions will need to accept to use a different irrlicht
for STK, otherwise they're just going to break STK. basically,
consider we are using a fork of irrlicht."

i.e. no.

Maybe the irrlicht developers can be convinced to change the way irrlicht is configured. (Preferably approach them knowing how it could be improved or with a patch.)

Add the supertuxkart patches to the Debian version of irrlicht,
building two sets of packages from one source package, one with the
patches, one without.
How would this be any less work than simply using the embedded copy of
irrlicht in stk's source? Building a set of binary packages just for
stk's use (libirrlicht-for-stk-{,dev,dbg,doc}) sounds just as painful
as statically linking irrlicht in stk.

No, in this way (security and other) patches are always applied to both libraries.


Reply to: