On Sun, May 2, 2010 at 9:53 AM, Pierre Schmitz <pierre@archlinux.de> wrote:
On Thu, 29 Apr 2010 12:05:19 -0500, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
That is going to be a painful initial rsync... Is it just the clean-up script that can not handle the change?
I'm sure we could figure something out... the cleanup script does one thing that is incompatible: it removes (rm) files from each repo if not in the DB - this assumes it is a symlink. It should be fairly easy to replace that with a "if symlink, rm, else mv to cleanup"
Can anyone else see anything incompatible here?
I think its really only the cleanup script that is directly affected. db-update doesn't need to know about old packages, db-move and db-remove only work on db files and use mv which should also work with symlinks.
I think it's definetly worth to modify the cleanup script to handle both layouts...a complete resync will produce a lot of unnessecary traffic.
How's this? http://code.phraktured.net/cgit.cgi/dbscripts/commit/?h=pkgpools&id=1e13a032ac0bef748150c60f3b670e57dad2aee5
The issue left is the community repo.
Ideas?