On 28/06/12 18:28, Edward Savage wrote:
On 28/06/2012, at 17:49, Toby Corkindale <toby.corkindale@strategicdata.com.au> wrote:
Hi, I wonder if I can get some advice from the list?
I want to run a little Debian repository -- but I have a requirement which seems to be missing from the software tried so far.
I want the repository to maintain multiple versions of the same package.
ie. So I could do this:
dput my-package_1.00-1_all.deb dput my-package_1.11-1_all.deb dput my-package_2.00-1_all.deb
And then on a machine using my repo, be able to say something like:
aptitude install my-package (> 1.10 & < 1.99) while on another machine, say: aptitude install my-package (>= 2.00)
So far, repo management software I've seen will purge the older version out when you upload a new one.
Any thoughts?
Thanks, Toby
Reprepro handles this really well. Check out its man page under the Override Files section and look for unused_files setting and the options for it.
Hi Edward, reprepro is actually the main one I've been trying to use. If I add version 1 of a package, and then version 2, it deletes version 1, as per: # reprepro includedeb squeeze /home/tobyc/testpkg_2_amd64.deb /home/tobyc/testpkg_2_amd64.deb: component guessed as 'main' Exporting indices... Deleting files no longer referenced... deleting and forgetting pool/main/t/testpkg/testpkg_1_amd64.deb I've had a look at the Override Files man page section, and I really can't figure out how to use the "unused_files" with it. The man page describes that as: Permit A list of options to allow things otherwise causing errors: unused_files Do not stop with error if there are files listed in the .changes file if it lists files not belonging to any package in it. Cleanup options A list of options to cause more files in the incoming directory to be deleted: unused_files If there is unused_files in Permit then also delete those files when the package is deleted after successful processing. Could you suggest the actual option that I should be applying here? Thanks, Toby