On Fri, Mar 20, 2009 at 11:04 AM, Abhishek Dasgupta <abhidg@gmail.com> wrote:
2009/3/19 Aaron Griffin <aaronmgriffin@gmail.com>:
I thought of that. The reason I decided not to was because some packages could move, say, out of testing for i686 and NOT x86_64. I don't know if that's a common case though.
Perhaps we can do this: move all packages by default. if the arch is specified on the command line, move only that arch. or in code -
looparches="${ARCHES[@]}" [ -n "$2" ] && looparches="$2"
for arch in $looparches; do .... do move logic here done
I just committed a patch to github for adding any architecture support to db-move and db-remove: http://github.com/abhidg/dbscripts/commit/67e112955482397bae1971fa60e1634a92...
I'm trying to figure out if it would make sense to also remove the old symlinks, or if the cleanup scripts would handle it just fine... I think the cleanup scripts would work The last thing on the list would be adding a block to the cleanup scripts to cleanup 'any' packages that don't have remaining symlinks... seeing as the 'any' dir doesn't have a real DB, we can't clean it up like normal, but if it symlinks to nothing, it can be deleted. Thanks for all your work on this, you're my hero - and the FIRST outside contributor to the db-scripts :)