SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Please forgive a stupid question gnashley:-)
I've installed src2pkg1.5 on my slackware 12 system. I've read the man page for src2pkg, but I'm a bit confused about how to create packages using src2pkg.
What would be the basic command for creating a slackware package in my installation directory? Let's say I want to build a package in /home/hitest/downloads
I'd like to try your program.
Thanks for any and all replies.
In the common case, just doing "src2pkg foo-1.0.tar.gz" or whatever should work. The resulting package will be in /tmp, and there will be a couple of working directories you may or may not want to get rid of (personally, I don't bother cause I set up /tmp to be mounted tmpfs, so everything dies on shutdown). Without a slack-desc it really isn't a valid package, but that doesn't matter much when it is strictly for personal use.
I usually always place each tarball in its' own directory -in your case:
Then just cd in there and run 'src2pkg super-new-prog-0.1.tar.bz2'
Note that src2pkg will insert a valid slack-desc file for you. If you want to generate it first along with a src2pkg build script for the package run:
src2pkg -N super-new-prog-0.1.tar.bz2
to create them. The script will be name super-new-prog.src2pkg.auto.Edit as needed/wanted and then run it using:
to execute the script.
The slack-desc file generated by src2pkg is named new.slack-desc. If you want to fill in the package description lines, just edit it like you want and then save it as simply slack-desc. Then it will be included in your package.
If you want to change the default location where temporary files are created and final packages are placed, read and edit the /etc/src2pkg/src2pkg.conf file.
I very much appreciate your helpful replies:-) I like to install Patrick's official Slackware packages, use SlackBuild scripts, and compile from source.
Your program gives me one more option to use, gnashley. Slackware is all about choice:-)
I'm going to go use your program now:-)
Very nice program:-)
Thank you for taking the time to build this for us, gnashley. This is a nice alternative to ./configure, make, and make install. Plus you get a solid slack package that can be easily upgraded.
Just finished making a slackware package for Sylpheed-2.4.1, it is one of my favourite light e-mail programs. Thanks again for your help:-)