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.
The biggest change in this release is that src2pkg now supports multi-lib and cross-compiler environments. If you are running Slackware64 with a multi-lib setup, you can use src2pkg to package 32-bit programs or libs by simply adding the option '-M32' to the src2pkg command-line. For other multi-lib systems or when cross-compiling, options are available which let you specify which compiler to use and which LIBDIRSUFFIX.
A small change has been made to the src2pkg 'API' which allows the use of a single 'build' function instead of separate functions for configure_source, compile_source and fake_install, similar to the 'build' functions used by other build systems. The 'build' function can also be used to simplify 'translating' regular SlackBuild scripts to the src2pkg format. Also, a new tool called 'sb2sp' is included which will automatically translate SlackBuild scripts for you. There are several advantages to doing this.
Support for drag-n-drop is now the default. A src2pkg-dnd script and desktop file make this possible. Unfortunately, it has only been tested with XFCE. I would appreciate it if any KDE users would try it out and report back with their results. src2pkg-dnd allows you to simply drop a tarball onto the src2pkg-dnd desktop icon to have a src2pkg script written for you. Dropping that src2pkg build script on the icon causes the build script to be executed from within an xterm.
This release has been nearly ready for two months now, but I've had such bad problems with my back that I was unable to do any productive work for all of July and August. Finally, this week, I was able to put the last changes in...
As always, bug reports, comments or suggestions can be sent to me directly at:
amigo AT ibiblio.org
Be sure to put 'src2pkg' in the subject line so I notice your message.
I'm especially interested to know if anyone has any troubles using src2pkg with Slackware64.
All right. First test drive of 1.9.9 is successful.
I previously used the older version of src2pkg to install a proprietary e-mail client (First Class) on my Slackware 13.0 system.
I just now used pkgtool to remove First Class. I used src2pkg-1.9.9 to successfully create a Slackware package from the First Class source tarball, it installed just fine. This was done on Slackware 13.0, XFce 4.6.1.
eddyvp -thanks a lot for trying that out -I never have KDE installed so was unable to check that out. Pieter Sartain did the heavy lifting to get it working for XFCE -I've been using it forever, but under ROX-filer/windowmaker which is different.
Hmmm, I'm not familiar with XFCE either :-(
Is there some command you have to run to update the database or create new icons?
Whether you do a fresh install or use upgradepkg, these two commands get run when the package is installed:
update-desktop-database -q usr/share/applications
gtk-update-icon-cache --quiet usr/share/icons
Hopefully piete will see this thread and chime in with some help...
First I've removed the previous version of src2pkg, then installed 1.9.9, but I guess and upgrade will also work just the same.
The icon appeared in the program menu, not on the desktop.
As instructed I've copied /usr/bin/src2pkg-dnd to my home directory, changed the ownership to eddy:users and created the icon on the desktop manually.
Compiled a few more tests (yakuake, kile) and all went alright.
Jeebiz, apparently you are trying to build firefox from source. (tuxdev was referring to installing the binary release) Of course, the Slackware SlackBuild just repackages the binary package released by the developers. In order to build Firefox from source, you must do it in a similar way to which seamonkey is built. This is not a job for the faint at heart -there is a good reason that PatV doesn't do it, because it is a *royal* PITA and can take days/weeks to get right.
The trouble is all about getting the right options. The Slackware build of seamonkey passes the options directly to the configure script so that autoconf is used. But, you can also place the options in a mozconfig file -this is the way most people do it. either way, discovering and choosing the right options is a real nightmare.
I have an old build script for firefox-1.0.7(the last GTK-1.2 version) which shows a good way to do it with src2pkg. here's an excerpt which shows the 'meat' of the src2pkg build script:
cp $CWD/mozconfig.FF-std-GTK1 $SRC_DIR/mozconfig
cd $SRC_DIR ; ./configure
MOZ_PHOENIX=1 make -j3 -s export
MOZ_PHOENIX=1 make -j3 -s libs
Of course, the trick is that I have a pre-made mozconfig.FF-std-GTK1 file which gets copied into the sources. For what it is worth, here are the contents of it:
The options for building a recent version would be considerably different -especially regarding the toolkit options. If you really want to build firefox from source, you could try starting out with a modified SlackBuild script for seamonkey. Or you could search the web(mozilla forums) for a viable mozconfig file to use as above.
Either way, set aside a month or so for achieving the package you want...
It would be nice if someone experienced with src2pkg would come up with a build script for a recent version -I won't touch the project because building it from source takes forever on my hardware -although recent sources can be built somewhat faster if built against an already-built xulrunner, I understand.