Greetings,
For some time, I have been creating my own Slackware packages of software, some of which may be of interest to the Slackware community. I once negotiated with linuxpackages.net, a Slackware package repository website I use, about putting my Slackware packages on their website. However, they required me to put my package on a 3rd party website or put up my own website, for them to look at my packages before they would put them on their website. They didn't have a place on their website where I could just "drop them off" for them to look at. I looked into what it would require for me to set up my own website, but when I discovered how much effort it would take to create and maintain a website I would like, I back-burnered the effort and haven't followed up on it.

So here's my question: Do you have any suggestions for submitting Slackware packages for the community to download and how did you go about it?

Thanks in advance.
Girvin Herr

weibullguy

11-05-2012 03:51 PM

Have you looked into slackbuilds.org?

dugan

11-06-2012 12:49 AM

Prebuilt packages are good, but SlackBuild scripts are better. Put them on GitHub if you don't want to submit them to SlackBuilds.org.

So here's my question: Do you have any suggestions for submitting Slackware packages for the community to download and how did you go about it?

SourceForge.net and code.google.com both will host source code (your SlackBuild script) and binary packages. I use Google Code for my Slackware packages.

But you should also submit your SlackBuild scripts to SlackBuilds.org.

dugan

11-06-2012 10:31 AM

Quote:

Originally Posted by w1k0
(Post 4823183)

To create and maintain the website isn't so hard.

If your webhost has directory indexes enabled, then all you really need to do is upload the SlackBuilds. You don't even need to create a website.

girvinh

11-09-2012 09:15 PM

I thank everyone who responded to my request. They were helpful.
As for Slackbuilds.org, my build scripts are much more complex and larger than the run-of-the-mill build scripts. They do a lot more error checking and respond to the standard --help and --version via getopt. They also allow a user build option for testing without being root. I discovered the hard way that building in /tmp can also be disastrous, so my build scripts use a safer /build instead. So, alas, my scripts do not meet the Slackbuilds.org requirements. So that rules out Slackbuilds as a distribution outlet. Unlike many package sites, such as LinuxPackages, my packages do include the build script.