From d424f431169f797d9e9b9e1439fe77865bde1e7c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 9 Aug 2021 16:00:57 -0400 Subject: [PATCH] comment --- ..._dd482d39c746dd6845382e9503731b6f._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/forum/standalone_tarballs_for_specific_versions/comment_25_dd482d39c746dd6845382e9503731b6f._comment diff --git a/doc/forum/standalone_tarballs_for_specific_versions/comment_25_dd482d39c746dd6845382e9503731b6f._comment b/doc/forum/standalone_tarballs_for_specific_versions/comment_25_dd482d39c746dd6845382e9503731b6f._comment new file mode 100644 index 0000000000..173963feae --- /dev/null +++ b/doc/forum/standalone_tarballs_for_specific_versions/comment_25_dd482d39c746dd6845382e9503731b6f._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 25""" + date="2021-08-09T19:50:11Z" + content=""" +It would take a significant amount of extra work, on an ongoing basis, for +the version output by the standalone build to match the version used for +the release. I would need to, after making a release, go build git-annex +against that tag, on multiple OS's. It is much easier to simply have an +autobuilder that builds current master, and when I make a release, ship the +most recent build. + +It's also some ongoing amount of work to respond to repeated +questions about it, when people notice that the version strings don't +perfectly match up, but I guess I've answered your questions about it now +and you won't be contributing to that workload further. Right? + +(The third way I could reduce the workload, which does seem more appealing +for some reason right now, would be to stop offering release builds.) +"""]]