On Fri, May 30, 2008 at 7:31 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Fri, May 30, 2008 at 7:25 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Fri, May 30, 2008 at 6:44 PM, <dpmcgee@gmail.com> wrote:
From: Dan McGee <dan@archlinux.org>
Move the extrapkg script to the name repopkg. All of the corepkg/extrapkg etc. scripts will retain their same behavior; however if the program is called with the name repopkg the first parameter passed will be used as the repository name to upload to.
Note that the non-existence of this directory on the remote end will probably result in failure.
Signed-off-by: Dan McGee <dan@archlinux.org>
Would you mind doing a: if name == repopkg: if $# -ne 1: omg abort! yell yell yell
I thought of this, but there are bigger problems. 1. scp options are there. You could end up trying to repopkg yourself into the -l repo 2. Uploading with a commit message: fix the download URL would send your upgrades to the 'fix' repository.
So [ $# -ne 1 ] wouldn't really do the full verification job at all.
oi vey! why can't scripts write themselves? when do we get robots to do this for us?