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

[Lockywolf]

I have a script for adding cargo links to the info-file:

https://gitlab.com/Lockywolf/lwfslackbuilds/-/blob/master/02_lockywolf-sbo-scripts/lwf_make-cargolinks.bash?ref_type=heads

Can't say it slows down things that much.
Downloading is a bit slower, but overall it's okay.

I would prefer not having custom-made tarballs hosted on private servers
when possible.

Charadon via SlackBuilds-users <slackbuilds-users at slackbuilds.org> writes:

> 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/


-- 
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240712/3498b579/attachment.asc>