<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 11, 2020 at 1:23 AM Caleb Maclennan <<a href="mailto:caleb@alerque.com">caleb@alerque.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Because the Git generated archive of the raw repository contents is not the same contents as the generated source packages. Specifically the former has no information about what version it is. The two ways to get this information are to have git history (i.e. you can use a clone of the repository to build) or to have a source build that has this generated information present (i.e. our generated version specific tarballs that have the relevant information cached inside).<br></div></div></blockquote><div><br></div><div>I do want to say: it's a bit of a nuisance to do testing this way, though. In order to generate a source tar, I have to successfully run CMake against the tree, which means I need all the devel dependencies installed on my machine. It's not impossible, but it is a bit of a pain. I'm all in favor of the CPack generators for Windows installers, but it's not terribly convenient for the source tar generation.</div><div><br></div><div>--Greg<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 10, 2020 at 5:41 PM Karl Kleinpaste <<a href="mailto:karl@kleinpaste.org" target="_blank">karl@kleinpaste.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<font face="FreeSerif">github release process automatically produces
tarfiles, zip and tar.gz.<br>
Yet our release machinery also produces tarfiles, tar.gz and
tar.xz.<br>
Why?<br>
</font>
</div>
_______________________________________________<br>
xiphos-devel mailing list<br>
<a href="mailto:xiphos-devel@crosswire.org" target="_blank">xiphos-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/xiphos-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/xiphos-devel</a><br>
</blockquote></div>
_______________________________________________<br>
xiphos-devel mailing list<br>
<a href="mailto:xiphos-devel@crosswire.org" target="_blank">xiphos-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/xiphos-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/xiphos-devel</a><br>
</blockquote></div></div>