On Tue, 08 Oct 2013 18:08:19 +0200, Ron Wilson <ronw.m...@gmail.com> wrote:
On Tue, Oct 8, 2013 at 11:56 AM, Doug Currie <doug.cur...@gmail.com>
wrote:
My repos integrate with packaging/build systems (some not under my
control) that would break if the archive name was changed by fossil.
Accessing URLs like
http://lua.sqlite.org/index.cgi/zip/lsqlite3_fsl09b.zip?uuid=fsl_9b
shouldn't add a SHA to the archive name.
We are talking about the generation of a name for a Zip/tar file when a
user selects the option to download a Zip/tar archive from the
repository.
Now it occurs to me that we already have a valid file name to use as a
base
for the Zip/tar file: The base name of the .fossil file. That file gets
created and named before the project name is set, so would be a
reasonable
candidate for the base name of the generated Zip/tar file.
I believe the recent fix (to make the prefix user-settable) goes in the
right direction (and is really sufficient as far as I'm concerned), so
what you propose might be another option here: a) define explicit prefix,
b) select "use basename of repo", c) use project name. let the developers
decide ...
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
