[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnupload --help examples
From: |
Karl Berry |
Subject: |
Re: gnupload --help examples |
Date: |
Fri, 27 Nov 2009 23:06:55 GMT |
Sure. These numbers were real Automake versions though,
I know.
want to genericize the package name as well?
Yep, that's what I meant to suggest.
--symlink also allows you to pass target names other than
*-latest.tar.gz I guess, so #2 shows how --symlink-regex works while
#3 shows how --symlink works?
I see. But since the examples are equivalent, it's not a very
interesting thing to show for --symlink. I think the examples should be
practical, not theoretical.
I guess I don't see the point in explaining --symlink, since
--symlink-regex already does what's desired, if symlinks are desired at
all. It's not like we are duty-bound to show an example for every
option. There are plenty of options already without examples.
Also, I think that a separate example should show uploading multiple
formats, instead of throwing it in with all the test uploads. In
general, I think all the examples should try to show just one new thing,
not many things mixed together.
I altered the last example to be about a mistaken upload, instead of
retiring an existing release. In general, it seems to me that we don't
want to suggest that it's a good idea to delete test (or any) releases.
I also didn't see any purpose to the "--" here, so I removed it.
0. Upload foobar-1.0.tar.gz to ftp.gnu.org:gnu/foobar
gnupload --to ftp.gnu.org:foobar foobar-1.0.tar.gz
Indeed, just goes to show why simple examples, and testing, are needed :).
Feel free to propose a patch that makes this more clear.
See below for my new text. If you want a patch instead, that's fine, I
just thought this would be easier to read.
If you know of a painless way to test these options, then I'm all
ears. I'm a big fan of testing all code.
I know of no easy (or even not so easy) way to test anything related to
ftp uploads, especially not with hypothetical package names and versions :(.
I think this is one case where you just have to take it
on faith/inspection and let users report the problems when they actually
try to instantiate them.
Thanks,
k
--------------------------------------------------
1. Upload foobar-1.0.tar.gz to ftp.gnu.org:
gnupload --to ftp.gnu.org:foobar foobar-1.0.tar.gz
2. Upload foobar-1.0.tar.gz and foobar-1.0.tar.xz to ftp.gnu.org:
gnupload --to ftp.gnu.org:foobar foobar-1.0.tar.gz foobar-1.0.tar.xz
3. Same as above, and also create symbolic links to foobar-latest.tar.*:
gnupload --to ftp.gnu.org:foobar \\
--symlink-regex \\
foobar-1.0.tar.gz foobar-1.0.tar.xz
4. Upload foobar-0.9.90.tar.gz to two sites:
gnupload --to alpha.gnu.org:foobar \\
--to sources.redhat.com:~ftp/pub/foobar \\
foobar-0.9.90.tar.gz
5. Delete oopsbar-0.9.91.tar.gz and upload foobar-0.9.91.tar.gz:
gnupload --to alpha.gnu.org:foobar \\
--to sources.redhat.com:~ftp/pub/foobar \\
--delete oopsbar-0.9.91.tar.gz \\
foobar-0.9.91.tar.gz