summaryrefslogtreecommitdiffstats
path: root/db-repo-add
AgeCommit message (Collapse)AuthorFilesLines
2012-04-29Source the config before the functions as the latter references the formerPierre Schmitz1-1/+1
2011-12-19Avoid calls to basenamePierre Schmitz1-1/+1
2011-11-05db-repo-add: At least check if the package to be added is available in the ↵Pierre Schmitz1-2/+2
correct directory
2011-11-05db-repo-{add, remove}: allow specifying multiple packagesDan McGee1-9/+11
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 McGee1-4/+4
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 Schmitz1-2/+1
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 Schmitz1-0/+40