On Mon, Apr 26, 2010 at 4:53 PM, Sam Sherlock <[email protected]> wrote:
> FWIW - I like the streamlinedness of what Avery is suggesting
Thanks.
> The current auto created tarballs have that naming structure so you can know
> at which point is was obtained.
That feature is extremely valuable; my suggestion is intended to
simplify the names without losing that feature.
> I have tried making a script that gets a tagged archive and unpacks it
> before running an install, I think I had issues with it since the tagged
> archives redirect to the archive (I might be wrong)
This is actually a slightly separate issue (although a real one). It
would be better if downloading the file used a content-disposition
header or something to set the filename. However, depending on how
the redirection works (I read somewhere that it uses Amazon S3 or
something, and S3 isn't very configurable) it might not actually be
fixable.
Note that if you download using, say, wget, it'll rename the file to
the name of the redirection target instead of the filename you give it
on the command line. But if you use, say, curl:
curl http://github.com/... >whatever.tar.gz
Then you have total control over the downloaded filename and can thus
avoid confusion. (I'm guessing this is what the Pause tool does, so
it never realizes anything funny is happening.)
Have fun,
Avery
--
You received this message because you are subscribed to the Google Groups
"GitHub" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/github?hl=en.
