Le 20/09/2017 10:04, Warren Young a écrit :
On Sep 19, 2017, at 3:22 PM, BohwaZ <boh...@bohwaz.net> wrote:
But I'm not sure if I want to implement that in Fossil just because
another unrelated piece of software makes bad decisions…
I think you have *two* uses of zip/tarball here, not one: Fossil’s
built-in mechanism for providing checkouts to people who can’t/won’t
install Fossil, and your release distribution mechanism.
If you want Fossil to be your HTTP file server for the latter case,
use its unversioned files feature from within your “make dist”
implementation. The Fossil project works this way: the Downloads page
contents on fossil-scm.org are not dynamically built, they’re static
unversioned files.
In Fossil anyone could just create a make recipe to generate a proper
ZIP file and sync it in the unversioned files instead.
That’s the province of your build system. Fossil is not a release
engineering tool. Fossil’s job stops when you tag the release.
Everything after that belongs to someone else, like Automake.
Fossil may then re-enter the picture with “fossil uv”, but that’s a
separate matter.
Yes I completely agree with you, this seems to be the right way of doing
things, it just requires more work on my side to adapt to Composer ;)
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
