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.

0 files changed, 0 insertions, 0 deletions