You are not logged in.
So how do others handle this when maintaining custom repos?
This command:
repo-add custom.db.tar.gz foobar-2.0-1.pkg.tar.xzWill add the package foobar-2.0-1 to the repo DB, removing any existing entries for "foobar" in the DB (eg, foobar-1.0.1), but the actual old on-disk package is not removed.
I can't use the package name and do `rm foobar-*.pkg.tar.xz` since that will also wipe out (for example) foobar-libs-2.0-1.pkg.tar.gz.
And trying to do it with a more specific rm wildcard such as foobar-*.*-*.pkg.tar.xz isn't generic enough to deal with packages like blahblah-5.14.9-1.pkg.tar.xz (with 3 parts to the version rather than 2)
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I manually do it - the Arch repos have automatic clean up tools (see the dbscripts project).
A config flag could be useful to add to repo-add. Add a feature request.
Offline
Thx Allan. I'll have a look at dbscripts.
I was pondering hacking it in myself (repo-(add|remove) are just bash scripts afterall) but I don't understand the delta stuff enough to do that ![]()
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline