[Slackbuilds-users] Rust program packaging woes

[fsLeg]

On 22.12.2024 00:51, B. Watson wrote:

> Frowned upon by whom? I'm a SBo admin, and I don't frown on it. In
> fact I do the same thing whenever I have to: host the source myself,
> if there's some reason the original source URL(s) won't do.

Ah. I just remembered that I read somewhere about not liking hosting 
sources. I now found where I read it: 
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2024-July/029497.html 
Turned out it was someone's single opinion.

> A tarball of vendor/ is preferred because it's the simplest way to
> do it, assuming you have a place to host it. If you don't, someone on
> this mailing list will probably volunteer to host it for you, or maybe
> give you write access to the sourceforge sbodirectlinks account (not
> sure who's in charge of that).

I do have a server, although since it's a private one I'm only concerned 
with it running when I need it, so there's occasional performance 
degradation or downtime when I perform maintenance tasks (overloaded 
Slackware server), also it might take time for me to discover when my 
server isn't available for some reason. But it's been working for many 
years with only short hiccups due to upstream issues.

> So you've got a python script that works and is more readable,
> maintainable than the shell script other builds use? Definitely
> include it in your build, and possibly it'll end up being mentioned in
> a (hypothetical so far) rust template.

Well, it's still a spaghetti code since I'm doing manually what is 
supposed to be done automatically by Rust's toolchain, but there's less 
voodoo happening, and I explained what vendoring function does in the 
source, I can also include comments for every step if it'll be helpful.

I also forgot to ask, do I need to provide a license for my helper 
script in the same way we do for SlackBuilds?