upgrades vs. installer packages
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At the moment, I'm currently developing packaging for "fahclient", a
distributed client for the Folding@Home project. The binary is available
from their website and it unredistributable. "fahclient" works by
downloading the file from upstream and providing a script that the user
can run to build a new package with it.
Remember that dpkg is not re-entrant; I can not install the built
package from my postinst since dpkg will be locked.
When the upstream file is upgraded, I will need to release a new
installer package. That's fine. But what happens when this is installed
on the users system? Because the user probably won't run the provided
script again, their client won't get upgraded.
I'd like the client (in the built package) to be upgraded when the user
upgrades their Debian system as normal. How can I achieve this?
At the moment, I'm thinking of letting postinst run the package build
script in the background and tossing a test at the top of my init.d
script which will install a newer version of the package if it exists.
Note that the init.d script is contained in the package being upgraded,
making this an exceptionally messy trick.
Are there any better approaches?
Thanks,
Nick Lewycky
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFB9/9MSGzVScQE0h4RAoS2AJ9102+3fOeMo5geSBUGjiXk9eCkcgCgxGxk
2sbtQFpk0dBDXYomZuxFXvU=
=F3v3
-----END PGP SIGNATURE-----
Reply to: