[Slackbuilds-users] Using a Git repo as the source

[Jeremy Hansen]

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:

https://github.com/csmith-project/creduce/archive/4ae77d1/creduce-4ae77d1e101135a6aea310b30c19e2af968b7bf6.tar.gz

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.

Jeremy

On Sat, Jun 8, 2024, 7:57 AM Shahab Vahedi via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> Hello list,
>
> TL;DR;
> What is the norm about grabbing source through Git?
>
> I want to prepare a package called "creduce" [1] for SlackBuilds.org.
> The thing about "creduce" is that some internal code of it, clang_delta,
> needs to be compiled with LLVM (headers), while the rest of the code can
> be built with g++.
>
> Using LLVM 13.0, as it exists in Slackware-15.0, leads to errors. The
> project team is aware of this [2] and a specific "llvm-13.0" branch [3]
> is provided to address that.
>
> So what I need to populate the source is something along these lines:
>
> $ git clone --single-branch --branch llvm-13.0 --depth 1 \
>             https://github.com/csmith-project/creduce.git
>
> I am wondering what's the best approach, from SlackBuilds scripts point
> of view, to tackle this? I have found some "git2tar{xz,gz}.sh" scripts
> for some packages. Could anyone give me a recent example of this or any
> other hints?
>
> Thank you,
> Shahab
>
> [1]
> https://github.com/csmith-project/creduce
>
> [2]
>
> https://github.com/csmith-project/creduce/issues/239#issuecomment-1014235777
>
> [3]
> https://github.com/csmith-project/creduce/tree/llvm-13.0
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240608/4a66ed16/attachment.htm>