[xiphos-devel] why produce tar files?

[Caleb Maclennan]

To ease testing purposes it's possible we could add a third fallback on a
dummy version number so that a raw source archive with no history or build
information could be built. This might be confusing for end users however,
I kind of prefer actually _failing_ to build if they are doing it wrong
rather than ending up with a successful build with garbage information.

For local testing purposes it's actually really easy to make a git-archive
buildable yourself, you just have to inject the version information. Just
`echo 0.0.0 > cmake/source_version.txt` after you extract. For now that's
the only blocker.

For CI testing purposes I think actually testing the whole process on the
generated source_package as we distribute to users is preferable.

There are a couple other things we could be doing with the built package
source that are impossible with git archives. One we could do signed
releases. Two we could get the rest of the vendored code out of the main
git tree while still including it in in the built sources. More come to
mind, but suffice it to say I think this is the right architecture.

On Mon, May 11, 2020 at 9:55 AM Greg Hellings <greg.hellings at gmail.com>
wrote:

>
>
> On Mon, May 11, 2020 at 1:23 AM Caleb Maclennan <caleb at alerque.com> wrote:
>
>> 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).
>>
>
> 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.
>
> --Greg
>
>>
>>
>> On Sun, May 10, 2020 at 5:41 PM Karl Kleinpaste <karl at kleinpaste.org>
>> wrote:
>>
>>> github release process automatically produces tarfiles, zip and tar.gz.
>>> Yet our release machinery also produces tarfiles, tar.gz and tar.xz.
>>> Why?
>>> _______________________________________________
>>> xiphos-devel mailing list
>>> xiphos-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/xiphos-devel
>>>
>> _______________________________________________
>> xiphos-devel mailing list
>> xiphos-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/xiphos-devel
>>
> _______________________________________________
> xiphos-devel mailing list
> xiphos-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/xiphos-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/xiphos-devel/attachments/20200511/48fb6520/attachment.html>