Are there plans to extend the templates SBo repository?

Originally Posted by willysr One issue with Go and Rust-based template is that they normally download things in the background unless you specify all the download lists in the .info which is very painful for the maintainer to follow on each release

Does Slackware at least have any documentation with recommendations for writing buildscripts for such software? I remember the SlackBuild-HOWTO from the pre-SBo templates repo and even pre-SBo era - it was useful. Is there currently something similar for Rust and Go software? Sure this way every person might eventually end inventing his own wheel, and after a while SBo can have buildscripts for Rust and Go software implementing different approaches. But this would be better than nothing. Nowadays, what are the options of a Slackware end user to get a missing third party Slackware package other than writing it himself?

Originally Posted by willysr One issue with Go and Rust-based template is that they normally download things in the background unless you specify all the download lists in the .info which is very painful for the maintainer to follow on each release

Originally Posted by solarfields any plans on changing SBo's policy on that?

The current policy is that SlackBuilds aren't allowed to download things. That is, the user should be able to download everything listed in the *.info file, disable network access, and then run the SlackBuild. Personally, I like such a policy. Are you suggesting the policy should change to allow the SlackBuild to download stuff? Anyway, such a discussion should take place on the mailing list, not here.

That doesn't mean bugs are prevented from slipping through, however. I try to remember to disable network access when testing my own scripts before submitting. But I'm too lazy to build everything from SBo like that.

Originally Posted by FlinchX Does Slackware at least have any documentation with recommendations for writing buildscripts for such software? I remember the SlackBuild-HOWTO from the pre-SBo templates repo and even pre-SBo era - it was useful. Is there currently something similar for Rust and Go software? Sure this way every person might eventually end inventing his own wheel, and after a while SBo can have buildscripts for Rust and Go software implementing different approaches. But this would be better than nothing. Nowadays, what are the options of a Slackware end user to get a missing third party Slackware package other than writing it himself?

If y'all keep asking maybe someone who already maintains Rust/Go packages will submit a template.

Originally Posted by drumz The current policy is that SlackBuilds aren't allowed to download things. That is, the user should be able to download everything listed in the *.info file, disable network access, and then run the SlackBuild. Personally, I like such a policy.

I like this policy as well, and I understand how this is a good design choice, for downloading things, there's sbopkg or similar. The show stopper for me isn't the policy, but lack of templates for these languages, as well as lack of general guidelines a la the old SlackBuild-HOWTO that I mentioned above (unless such a thing exists and I don't know about it).

But also I can't deny the fact that the amount of useful software written in Rust and Go is on the rise and that I don't want to choose either another distro, or use some kind of chroot/container/vm/appimage/whatever hack to be able to make use of such software in Slackware without increasing system maintenance time.

I just thought that the pre-release moment is a good moment to get some feedback on it, so this problem doesn't stay in its current state till the next stable release.

Originally Posted by drumz If y'all keep asking maybe someone who already maintains Rust/Go packages will submit a template.

This would be great, especially paired with threads in this forum for each, where people with zero experience about such specific SlackBuilds could ask questions.

Originally Posted by drumz The current policy is that SlackBuilds aren't allowed to download things. That is, the user should be able to download everything listed in the *.info file, disable network access, and then run the SlackBuild. Personally, I like such a policy. Are you suggesting the policy should change to allow the SlackBuild to download stuff? Anyway, such a discussion should take place on the mailing list, not here. That doesn't mean bugs are prevented from slipping through, however. I try to remember to disable network access when testing my own scripts before submitting. But I'm too lazy to build everything from SBo like that.

I know what the current policy is and I also like it. I am not suggesting anything, although I think some flexibility should be possible.

Anyway, such a discussion should take place on the mailing list, not here.

Why is that? LQ seems the perfect place for such discussion.