[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Sat, 16 Jun 2012 11:44:41 +0100 (BST) Gordon Henderson <gordon+lug@xxxxxxxxxx> wrote: > Ideally, I need my package to replace an existing package if it's already > installed, or to stop a future update replacing my package with the older > version off Debian. (Let's not wory about security concerns for now - > unlikely to be any, however) > > So what do I do? Increment the version number? Or is there some better way > of doing it? Use an epoch. That way, your version will always be newer, it's easy to keep track of the underlying Debian version in use and it's is trivial to remove if the changes are merged. (You just need to remove the old epoch version from your local repository and specify the Debian version explicitly and apt will 'downgrade'.) 1.2.5-2 becomes 1:1.2.5-2 and when 1.2.6-1 turns up, 1:1.2.5-2 is still newer. > And it's rather critical that I maintain the ability to do this as serial > is not a viable option for this project, however it might well be used by > 100's or even 1000's of people, so needs to be as easy to install as > possible - wget the new version off my site, and dpkg -i is acceptable, > but a future apt-get update/upgrade overwriting it isn't... Contact the Debian maintainer and discuss your requirements and whether the package can be adapted to provide both implementations. -- Neil Williams <linux@xxxxxxxxxxxxxx>
Attachment:
pgpdpTJKPLhHx.pgp
Description: PGP signature
-- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq