Re: packages with binary 'source' files
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Why should the debian.diff contain this binary file, that is not part
> of your port to Debian, but a result of compiling the package?
True
> As the diff is generated at the very beginning of dpkg-buildpackage,
> this means that it was left over from a previous compilation and make
> clean is broken to not remove it.
The binary file takes a long time to generate (several hours on my venerable
P233) so make clean does not remove it. I'm not sure if leaving it is the
correct behaviour or not.
I'm going to learn how to create multi-binary packages, then maybe I can
distribute the binary file as a seperate package and make the .diff simpler.
I think I'll still have to uuencode it since the binary file isn't arch
independant (depends on endian).
Corrin (with a correct sig this time...)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6pWA29o3gUBuxj/sRAs8dAJ40Nlp0bDsqHxVi3+Jbkb+OWFRZdACcCsPm
kbKzzGEpOBTtxrtum28+OUc=
=OpSH
-----END PGP SIGNATURE-----
Reply to: