On Sat, May 23, 2015 at 7:47 AM, Richard Hipp <d...@sqlite.org> wrote:
>
> Fossil version 1.33 has been tagged. Binaries are available on the
> download page: https://www.fossil-scm.org/download.html
Richard,
Very nice! One thing I noticed is that the source directory name upon
extracting the tar.gz is different in this release compared to 1.32. 1.32
extracted to fossil-1.32, and 1.33 extracts to fossil-src-1.33. I don't
particularly care what the convention is, but if it could be consistent
between releases, that would make it a bit easier for packagers. For
example, for HaikuPorter, it assumes by default that the source directory
will be {program-name}-{program-version}, which in my case makes the
packaging easier using the 1.32 convention. I presume that other packaging
systems may look at the filename itself and use everything before the
.tar.gz as the default source directory. That would make the 1.33
convention work just fine.
Do you suggest I simply update my build recipe to the fossil-src-{version}
convention, or do you think it would be better to upload a new tar.gz using
the previous fossil-{version} convention? I know this whole source
directory naming convention has been discussed in the past [1] [2], so
sorry to have to bring it up once more. Again, I don't really care what is
decided, but want to know how to proceed before I commit my build recipe
and start creating packages.
Thanks!
- joe
[1]
http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg19161.html
[2]
http://www.mail-archive.com/fossil-dev%40mailinglists.sqlite.org/msg00041.html
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
