summaryrefslogtreecommitdiff
path: root/db-repo-remove
AgeCommit message (Collapse)Author
2016-04-17Consistently use "$(dirname "$(readlink -e "$0")")"Luke Shumaker
This does correct handling of - executing a program by symlink - any weird characters in the full path - I'm sure there's another case I thought about when I originally did this.
2016-04-16Use printf-formatters instead of string interpolation on msg, error, etc.Luke Shumaker
2016-04-16Fix quoting around variables, especially arrays.Luke Shumaker
Other than pure quoting, this involved: - swapping */@ for array access in a few places - fiddling with printf in a pipeline - replacing `$(echo ${array[@]})` with `${array[*]}` - replacing `echo $(...)` with `...` When searching for these things, I used the command: grep -Prn --exclude-dir=.git '(?<!["=]|\[\[ |\[\[ -[zn] )\$(?!{?#|\(|\? )' and ignored a bunch of false positives.
2012-04-29Source the config before the functions as the latter references the formerPierre Schmitz
2011-12-19Avoid calls to basenamePierre Schmitz
2011-11-05db-repo-{add, remove}: allow specifying multiple packagesDan McGee
This allows invoking these commands for more than one package at a time which is incredibly more efficient as the database doesn't need to be locked, unpacked, modified, changed, and unlocked for every single passed package name or file if you have more than one. Signed-off-by: Dan McGee <dan@archlinux.org>
2011-11-05db-*: always handle pkgname/pkgbase/pkgfile argument lastDan McGee
This matches what we do in db-update, and makes the most sense if we want to expand these commands to take multiple arguments at the same time. Especially in the case of db-repo-add and db-repo-remove, these wrapper commands should be no more limiting than repo-add and repo-remove which always allow multiple arguments and are more efficient that way. This patch simply reorders the arguments; a later patch will support multiple pkgname/pkgbase/pkgfile arguments on the command line. Although this does break backwards compatibility and requires some changing of muscle memory, I think it is a worthwhile change to make as the functionality of these commands becomes more powerful and the order of arguments becomes the same in all of them. Signed-off-by: Dan McGee <dan@archlinux.org>
2011-01-15Move repo manipulation code into common functionsPierre Schmitz
repo-add and repo-remove is now indirectly called by arch_repo_add/remove. This simplifies future extensions like incremental file list creations. See FS#11302
2010-11-22Add wrappers for repo-add and repo-removePierre Schmitz