<div dir="auto">You can download any single commit as a tarball and use that as your source. If you want the current latest commit in that llvm-13.0 branch, you'd use: <div dir="auto"><br></div><div dir="auto"><a href="https://github.com/csmith-project/creduce/archive/4ae77d1/creduce-4ae77d1e101135a6aea310b30c19e2af968b7bf6.tar.gz">https://github.com/csmith-project/creduce/archive/4ae77d1/creduce-4ae77d1e101135a6aea310b30c19e2af968b7bf6.tar.gz</a><br></div><div dir="auto"><br></div><div dir="auto">This is better than using the HEAD reference, since the md5 would change (and compilation could possibly break) if the developers add any new commits.</div><div dir="auto"><br></div><div dir="auto">Jeremy</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 8, 2024, 7:57 AM Shahab Vahedi via SlackBuilds-users <<a href="mailto:slackbuilds-users@slackbuilds.org">slackbuilds-users@slackbuilds.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello list,<br>
<br>
TL;DR;<br>
What is the norm about grabbing source through Git?<br>
<br>
I want to prepare a package called "creduce" [1] for SlackBuilds.org.<br>
The thing about "creduce" is that some internal code of it, clang_delta,<br>
needs to be compiled with LLVM (headers), while the rest of the code can<br>
be built with g++.<br>
<br>
Using LLVM 13.0, as it exists in Slackware-15.0, leads to errors. The<br>
project team is aware of this [2] and a specific "llvm-13.0" branch [3]<br>
is provided to address that.<br>
<br>
So what I need to populate the source is something along these lines:<br>
<br>
$ git clone --single-branch --branch llvm-13.0 --depth 1 \<br>
            <a href="https://github.com/csmith-project/creduce.git" rel="noreferrer noreferrer" target="_blank">https://github.com/csmith-project/creduce.git</a><br>
<br>
I am wondering what's the best approach, from SlackBuilds scripts point<br>
of view, to tackle this? I have found some "git2tar{xz,gz}.sh" scripts<br>
for some packages. Could anyone give me a recent example of this or any<br>
other hints?<br>
<br>
Thank you,<br>
Shahab<br>
<br>
[1]<br>
<a href="https://github.com/csmith-project/creduce" rel="noreferrer noreferrer" target="_blank">https://github.com/csmith-project/creduce</a><br>
<br>
[2]<br>
<a href="https://github.com/csmith-project/creduce/issues/239#issuecomment-1014235777" rel="noreferrer noreferrer" target="_blank">https://github.com/csmith-project/creduce/issues/239#issuecomment-1014235777</a><br>
<br>
[3]<br>
<a href="https://github.com/csmith-project/creduce/tree/llvm-13.0" rel="noreferrer noreferrer" target="_blank">https://github.com/csmith-project/creduce/tree/llvm-13.0</a><br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div>