[Slackbuilds-users] brave-browser-the-latest broken weeks

B. Watson urchlay at slackware.uk
Thu Sep 25 20:03:36 UTC 2025


I'm not sure I follow everything you said but I'll try to respond
to the bits I do understand...

On Thu, 25 Sep 2025, David Chmelik wrote:

> Lately I download .deb on GUI WWW and usually need download manager to 
> resume: these days GitHub (GH) is even occasionally inaccessible and 
> commonly timeouts/restricted for large WWW downloads.

Use wget. It will reconnect/continue automatically. Even if a download
fails and leaves a partial file, you can use "wget -c" to continue
where it left off.

I haven't personally run into "github is inaccessible" or had
downloads from it fail. Maybe there's a problem with your ISP?

> Another option is if you can document where we can put .deb for 
> brave-browser-the-latest, like standard for sbopkg is /var/cache/sbopkg, 
> sbotools /usr/sbo/distfiles:

If you're running SlackBuilds manually, without a tool like sbopkg
or sbotools, the "source" (the .deb, in this case) goes in the same
directory as the .Slackbuild and .info files. That's covered in the
FAQ on our site, I'm surprised you're having trouble with this.

If you're using sbopkg or sbotools, the standard location is defined
by the tool's author. It has nothing to do with slackbuilds.org
itself, our documentation is only for the stuff we actually created.
See the documentation for the tool.

This mailing list isn't really for sbopkg or sbotools discussion, I'm
sure those tools have their own mailing lists. It's not *forbidden*
to talk about them here, it's just not likely to be fruitful.


More information about the SlackBuilds-users mailing list