[Slackbuilds-users] sbosubmit: SlackBuilds.org command line submission tool

Andrzej Telszewski atelszewski at gmail.com
Tue Sep 27 21:29:32 UTC 2016

On 27/09/16 22:59, Arkadiusz Drabczyk wrote:
> On Fri, Sep 09, 2016 at 03:43:09PM +0200, Andrzej Telszewski wrote:
>> Hi,
>> I have written command line submission tool for SlackBuilds.org
>> Before going public, I would like to ask you to give it a try and report
>> back any problems you might find.
>> As of now, I consider the tool to be feature complete (more options will
>> come one day), so please report back only possible errors rather than
>> features requests.
>> Source code together with SlackBuild for it can be found here (once tested,
>> it will get removed):
>> http://www.telszewski.net/software/src/sbosubmit/
> Hello Andrzej,
> I just used your tool and it seems to work, thank you for your work!

I'm really happy to hear that :-)
I can see that you sent your SlackBuild to both the testing server and 
SlackBuilds.org server ;-)

> Just one tiny remark - I accidentally had a source tarball (~2.8 MB)
> in a directory where I used sbosubmit and it failed with the following
> message:
> [II] creating archive...
> [EE] archive: Buffer exhausted
> It comes from libarchive and is probably caused by too large size of
> output archive.  In current form it's quite uninformative to the user.
> Shouldn't it be changed to something better?

The buffer size is set to 1MiB. That's actually the maximal archive size 
SlackBuilds.org would accept.

I could probably report a differently worded message, although there is 
no way to tell what the archive size should be (other than it should not 
exceed the 1MiB).

I personally do not place the source code tarball directly in the 
SlackBuild directory, but rather soft-link it to the source code tarball 
that is located under my "central" tarballs store.

Using soft-linked tarball is preferred when working with sbosubmit, 
since soft links are skipped when creating the submission archive. This 
way you won't accidentally send the source code tarball within 
submission archive.

For the record, a directory named "tmpdir" is skipped too, and it can be 
used as playground when developing the SlackBuild.

> IMO though it would be the best if we just sent new submissions and
> updates as patches directly to the mailing list as it was done during
> the transition from 14.1 to 14.2 instead of using the submission form.
> It only takes 2 commands - git-format-patch and git-send-email, much
> faster and comfortable.

Switching to git would be a sad day for sbosubmit ;-)
BTW, sbosubmit is only one command to type :-^

Once more, thanks for testing and reporting back!

> (BTW, message sent through gmane.org do not show up on the list.  Does
> anyone else here use gmane.org?)

Best regards,
Andrzej Telszewski

More information about the SlackBuilds-users mailing list