Re: Warzone 2100 packaging status report
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eddy Petrișor wrote:
>> I have purged the changelog, because the data it contained is now
>> irrelevant. (Eddy, what is the point of build-depending on dpkg-dev? It
>> is build-essential, is it not?)
>
> You use a feature (the variables that allow bin NMUs) which is present only
> in dpkg-dev 1.13.19 or later. You have to have a versioned dependency on dpkg-dev.
But why should anyone care? Even Stable now has 1.13.25. In any case, I
would consider versioned build-conflicts a cleaner solution.
>> The package is set to Architecture: any, but this may not be the best
>> option. Warzone 2100 does not officially support 64-bit architectures,
>> and insists on being built as 32-bit application.
>
> Maybe we can patch that (I have a 64 bit system ;-)
The official position is "not possible with 2.0, maybe in 2.1". I found
some patches that are said to bring initial support for 64-bit systems,
but I have not yet managed to find out where they ended up. Will try the
latest SVN some time later this week.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGLPRnztOe9mov/y4RAmRsAJwOlsnoJOsetWH52sPZ7NQlwxzLegCfZ2UX
re2JCL3sXqrUudaHyOi7gTQ=
=Hm9i
-----END PGP SIGNATURE-----
Reply to: