SlackwareThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Without more information it is going to be pretty difficult for anyone to help you troubleshoot. "It doesn't work" is not a very complete error report. What are the contents of these packages you are creating? Slackware packages are compressed tar files, so looking at the contents is easy enough to do. How are you verifying nothing is being installed? Also, some software requires special handling. Simple online instructions for creating a package may not work in all cases.
Is there some reason you aren't using the httpd-2.2.19 package that is already part of Slackware 13.1? If you want to customize the build in some way you could download the source directory for httpd from your favorite Slackware mirror, change the configuration options, and rebuild.
Mike is right, you really shouldn't replace stock slackware packages unless you've got a good reason. If you do, just modify the slackbuilds from the slackware official mirrors.
Additionally, the steps mentioned in that tutorial will not work for all packages. You should always read the installation instructions of a particular package.
The Apache httpd package supplied with 13.1 is 2.2.15
That is what initially shipped with Slackware 13.1 when it was released. It has since been upgraded to 2.2.19. Look in the patches/ directory of your favorite Slackware mirror for either the binary package or the source.
If you aren't already, you may want to subscribe to the slackware-security mailing list so that you are made aware of these security updates, including the download URL to update itself. If you're still running Apache httpd 2.2.15 on a Slackware 13.1 machine, you missed out on four security notifications and updates.
But i really still want to learn how to make packages for slackware.
In the cases of Apache and Python, the sources for building the packages are available on any Slackware mirror. You just download the slackware(64)-$VERSION/source/whatever directory. In that directory, you'll find a file whose extension is .SlackBuild. Run that .SlackBuild, and the package will be built. If you want to change things, then just edit the SlackBuild file.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Looking at the link you supplied it recommends changing to the build directory pkg and running makepkg pkgname which worked in Slackware-12.2 but will not work in Slackware-13.1 giving you "ERROR: Can't make output package in current directory.". I'm not sure why you are not seeing this error reported from makepkg.
You now have to build a package outside of the directory you are building a package in - which make sense. So makepkg ../pkgname will work but not makepkg pkgname whilst in the pkg directory in which you have built the package.
Credit for wanting to build then install packages rather than the simple configure,make,make install source building as package management makes your system far more maintainable and robust.
As others have suggested I highly recommend looking at Slackbuild scripts, after all Slackware itself was built this way, and figuring out how they work. The source directory on the Slackware repos have Slackbuild scripts showing how the components of the distro were built - very educational.
Credit for wanting to build then install packages rather than the simple configure,make,make install source building as package management makes your system far more maintainable and robust.
Thanks.
Thats excactly why i want to know how to make packages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.