-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Gilbert wrote:
> is there a policy on whether an executable is permitted to update
> itself?
Not sure about The Policy, but I can see a lot of reasons why this
should not be done:
1. The md5 sums will not match anymore, so one cannot
verify the integrity of the file.
2. The actual version of application will be different
from the one reported by apt, so future upgrades may
actually downgrade the application.
3. Version information in bug reports may be wrong.
4. The upstream build may not work because of mismatched
dependencies.
5. The upstream build may introduce bugs.
6. The upstream build may not be DFSG free.
7. Etc. etc...
Sounds like reinventing the wheel, only the wheel is now square. Do not
do this, please.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFqhCLztOe9mov/y4RAsVtAKCeruq2iYKoQCZfE37xzEYMIHLPSgCeJ+3l
fmbE29MxAyy0pI7mVLiaa9s=
=0cIO
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
