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.
src2pkg has a new home. After a recent crash on my hosts'(ibiblio.org) server all my files(over 15GB) were gone.
So, while repopulating the site I decided to reorganize it as well. This means that old links to my site are broken including the ones to src2pkg.
There is a new release available with several new features and improvements.
Everything on my site was destroyed about 2 months ago and I am still working on getting everything ready to re-populate it. There were more than 500 packages there so getting it all back is a bit of a chore, especially because I'm updating the scripts and rebuilding the packages.
Src2pkg looks good, but it uses installwatch like you pointed out. Perhaps the idea of making this is laughable to many of you, but this is a really frustrating problem. I want absolute control over where the install program writes files. I will look further into this. Thanks.
Thanks for the tip, but the problem is not that all the material is lost. I mean I have everything here on hard drive -I just need to re-upload everything. I was waiting to finally get flat-rate service this month and to make some decisions about how to layout the new site.
The site you mention has a pretty old copy of the site which may be useful to someone. Actually I'm glad in a way that all the content was lost on most mirrors since quite a few of them had very old material which I had retracted from the main site for various reasons.
I've just spent the afternoon trying to write a slackbuild script, unsuccessfully. I gave src2pkg a go, and it worked first time. I was trying to build a very simple program called ee (easyedit), but I couldn't set the DESTDIR variable in the build script. So how does src2pkg do it? Whenever I ran my slackbuild script some things such as the man page would get installed before I'd actually installed the package.
The 'Makefile' specifies this.
cp ee /usr/local/bin/ee
cp ee.1 /usr/local/man/man1/ee.1
There is no DESTDIR that I could set. What's the way around this?
Generate a src2pkg script using the -N option (src2pkg -N tarball-name)
Then open it and comment the install routine out like this:
Then add these lines to the src2pkg script just after that:
mkdir -p $PKG_DIR/usr/bin
cp -a $SRC_DIR/ee $PKG_DIR/usr/bin
mkdir -p $PKG_DIR/usr/man/man1
cp -a $SRC_DIR/ee.1 $PKG_DIR/usr/man/man1
You could also create a patch for the Makefile. I usually use 'gendiff' which is part of the rpm package to make them.
Make a copy of the Makefile named Makefile.00, then modify it like this:
cp ee /usr/bin/ee
cp ee.1 /usr/man/man1/ee.1
Then, run 'gendiff . .00 > ee-version-fix-paths.diff' and copy the resulting patch into the same directory as the src2pkg script.
I did actually patch the Makefile to install the executeable and the man page to /usr instead of of /usr/local. The problem is they get installed by running the ee.SlackBuild script, which obviously they shouldn't. There must be something wrong with my script. The example scripts I've seen use a DESTDIR $PKG variable when running 'make install'. So I'm assuming that's what isn't working. src2pkg didn't have any trouble with it.