summaryrefslogtreecommitdiff
path: root/abslibre
diff options
context:
space:
mode:
authorLuke Shumaker <lukeshu@sbcglobal.net>2015-06-05 00:48:12 -0600
committerLuke Shumaker <lukeshu@sbcglobal.net>2015-06-05 00:51:12 -0600
commitb96b9d95dd4d2214a428f1435a9a72ef50f43cf5 (patch)
treee8204ebe8ef806fe2affea7da12eff72dddc494d /abslibre
parent003288a90c042c56d86258f60ac205b1d3053eab (diff)
db-update: Hook in to `xbs release-server` as it exists today.
Obviously, this is an exercise in noticing a leaky abstraction. - assumes that the PKGBUILD is staged to a real directory going in - assumes where that is - assumes how to clean that up I believe the correct solution will require modifying XBS. Following is what I believe the changes should be. - change release-server to take "REPO ARCH DIR1 [DIR2...]", instead of using the CWD. - but this still assumes that the caller knows where release-client put the PKGBUILD, so change it to take "REPO ARCH PKGBASE1 [PKGBASE2...]". - this means that release-server knows to check if a PKGBUILD exists at the specified arch, and fall back to 'any' if it doesn't. - an alternative would be passing in the .pkg.tar filenames, and either parsing the filename or using db-functions to figure out the arch. - ??? how to get rid of cleaning up assumptions.
Diffstat (limited to 'abslibre')
0 files changed, 0 insertions, 0 deletions