[Slackbuilds-users] Questions with packaging a rust program.

[fourtysixandtwo]

Hi Charadon,

I have been doing that for a little while now with some python/rust
builds and filtering for a limited selection of linux rust targets to
keep the size down.  You'll want to install the
"cargo-vendor-filterer" slackbuild first.  Then have a look at my
"python3-maturin" slackbuild.  I include a stub "mkvendored.sh" script
that calls another script I include with cargo-vendor-filterer
"/usr/bin/cargo-mkvendored.sh".

Let me know if you have any questions.

Cheers

On Thu, Jul 11, 2024 at 1:03 PM Charadon via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
>
> Hey all,
> I'm wanting to make a Slackbuild for BLAKE3. The issue is that it's made
> in rust. Now rust has a thing that makes it pretty easy to vendor
> (`cargo vendor`) the dependencies, the issue is that, unless upstream
> provides their own vendored tarball, you'll be making your own.
>
> So here are my questions:
>
> 1. Can I make a vendored tarball, upload it somewhere like archive.org
> and use that as a source? I know this is questionable security wise, but
> you should be able to replicate the archive using a `git clone` and
> `cargo vendor`
> 2. If not, can I include a script that downloads the source, runs cargo
> vendor, and makes a vendored tarball?
> 2. If not, how would you go about packaging a rust program? Is there any
> guide anywhere?
> _______________________________________________
> 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/
>