On Tuesday, 20 September 2016 1:37:41 PM AEST Markus Koschany wrote: > > I still think that a build-conflicts is the wrong option when you can make > > it build with both packages installed. My patch allows it to build > > regardles of any other packages installed. > > > > Why do you think that build-conflicts is the right solution? > > Currently the game can only be built with automake1.11. That is even > enforced with the revert-372eff6693e633e8d0d1d0b8a9ceb996a5c3f49f.patch. > > Maybe you forgot to include your patch in the debian directory that you > attached to the bug report. When I build without automake1.11 the > package FTBFS.
My patch makes it call automake1.11 directly even if other versions are installed. The automake packages on Debian are specifically configured to support this. > So this patch needs an update but building with the default automake is > of course the preferred solution. Automake is very painful to use. If upstream wanted to support a newer version then we could do it as an upstream thing. But supporting a different version of automake in a Debian patch isn't practical. > By the way the package builds fine in a clean environment even without > the Build-Conflicts option, that's why I downgraded the severity. Like most serious Unix users I have many programs I compile and I don't want to be uninstalling packages before compiling them. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
