Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
11-05-2012, 02:01 PM
|
#1
|
|
LQ Newbie
Registered: Mar 2011
Posts: 17
Rep:
|
Where to post my own Slackware packages?
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
|
|
|
|
11-05-2012, 02:51 PM
|
#2
|
|
ReliaFree Maintainer
Registered: Aug 2004
Location: Kalamazoo, Michigan
Distribution: Slackware, Cross Linux from Scratch, Gentoo
Posts: 2,663
Rep: 
|
Have you looked into slackbuilds.org?
|
|
|
|
11-05-2012, 11:49 PM
|
#3
|
|
Senior Member
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 3,668
|
Prebuilt packages are good, but SlackBuild scripts are better. Put them on GitHub if you don't want to submit them to SlackBuilds.org.
|
|
|
|
11-06-2012, 02:03 AM
|
#4
|
|
Senior Member
Registered: May 2008
Location: Poland
Distribution: Slackware, Mint
Posts: 1,232
Rep: 
|
To create and maintain the website isn't so hard.
Use the following code:
Code:
<HTML>
<HEAD>
<TITLE>My own Slackware packages</TITLE>
</HEAD>
<BODY>
<H1>My own Slackware packages</H1>
<H2>My good Slackware package 1.0.0</H2>
<P><A HREF="my_good_slackware_package-1.0.0.tar.gz">my_good_slackware_package-1.0.0.tar.gz</A>
<H2>My better Slackware package 1.2.3</H2>
<P><A HREF="my_better_slackware_package-1.2.3.tar.gz">my_better_slackware_package-1.2.3.tar.gz</A>
<H2>My best Slackware package 3.2.1</H2>
<P><A HREF="my_best_slackware_package-3.2.1.tar.gz">my_best_slackware_package-3.2.1.tar.gz</A>
</BODY>
</HTML>
and replace the sample text with your own.
|
|
|
|
11-06-2012, 08:14 AM
|
#5
|
|
Member
Registered: Sep 2009
Distribution: Arch Linux
Posts: 40
Rep:
|
Binary package hosting
Quote:
Originally Posted by girvinh
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.
|
|
|
|
11-06-2012, 09:31 AM
|
#6
|
|
Senior Member
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 3,668
|
Quote:
Originally Posted by w1k0
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.
|
|
|
|
11-09-2012, 08:15 PM
|
#7
|
|
LQ Newbie
Registered: Mar 2011
Posts: 17
Original Poster
Rep:
|
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.
Thanks again for all the suggestions.
Girvin Herr
|
|
|
|
11-10-2012, 01:36 AM
|
#8
|
|
Member
Registered: Nov 2010
Distribution: Slackware64 -current
Posts: 82
Rep:
|
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 09:27 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|