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.
i just use Slackware's very own makepkg providing the source code supports DESTDIR, what i do is make a directory named pkg as /tmp/pkg then when "make" sucessfully builds the source i run make install DESTDIR=/tmp/pkg then with the terminal i cd to /tmp/pkg and run makepkg /tmp/pkg/package_name.tgz
always keep /tmp/pkg completely empty after you make your package (store the package somewhere else) or the previous package will be bundled with the next package you make...
Last edited by Okie; 05-05-2008 at 09:49 AM.
Reason: fixed typo
i just use Slackware's very own makepkg providing the source code supports DESTDIR, what i do is make a directory named pkg as /tmp/pkg then when "make" sucessfully builds the source i run make install DESTDIR=/tmp/pkg then with the terminal i cd to /tmp/pkg and run makepkg /tmp/pkg/package_name.tgz
always keep /tmp/pkg completely empty after you make your package (store the package somewhere else) or the previous package will be bundled with the next package you make...
Thanks for the reply. I do know how to compile from source. I'm curious about gnashley's utility as it creates nice Slackware packages.
Hello, hitest. Congrats! I've let your question goad me into finally uploading the latest sr2pkg which has been quite awhile in the making.
More directly to your question, yes src2pkg-1.9.5 will work okay with Slack-12.1. However, the new version includes a great number of improvements -both small and large. It has gone through a very long testing period here on my systems, but I've only released a pre-release version to a couple of contributors.
I'd be pleased to have you be the first to try the new version. If you are installing fresh to Slack-12.1, just install the src2pkg-1.9.6-noarch-3.tgz package from here: http://distro.ibiblio.org/pub/linux/...6-noarch-3.tgz
Then run 'src2pkg --setup' as user 'root'. Then it should be ready to use. This new version is designed so that you won't have to re-run 'src2pkg --setup' when upgrading to a later version -at least until further notice. This command now creates and installs a separate package which contains the binaries and libs used by src2pkg -this means they remain installed when upgrading src2pkg itself. Upgrading these progs (the package is named 'src2pkg-helpers') should rarely be necessary and I'll always notify you when it is. I've added several programs from the coreutils package to the src2pkg-helpers installation which I think will eliminate any possible problems associated with later glibc versions.
I'm going to post a separate announcement of the new version which will contain some other useful information.
I've tried it on the latest Xmoto version, which wouldn't compile with a SlackBuild script. With src2pkg it went fine.
It's the only experience I have with src2pkg so far on SW 12.1 though, haven't used it on anything else (all the rest is compiled and installed through SlackBuild scripts from SlackBuilds.org).
EDIT:
I hadn't read Gnashley's posting when I posted mine.
Thanks Gnashley, scr2pkg rocks!
Hello, hitest. Congrats! I've let your question goad me into finally uploading the latest sr2pkg which has been quite awhile in the making.
More directly to your question, yes src2pkg-1.9.5 will work okay with Slack-12.1. However, the new version includes a great number of improvements -both small and large. It has gone through a very long testing period here on my systems, but I've only released a pre-release version to a couple of contributors.
I'd be pleased to have you be the first to try the new version. If you are installing fresh to Slack-12.1, just install the src2pkg-1.9.6-noarch-3.tgz package from here: http://distro.ibiblio.org/pub/linux/...6-noarch-3.tgz
Then run 'src2pkg --setup' as user 'root'. Then it should be ready to use. This new version is designed so that you won't have to re-run 'src2pkg --setup' when upgrading to a later version -at least until further notice. This command now creates and installs a separate package which contains the binaries and libs used by src2pkg -this means they remain installed when upgrading src2pkg itself. Upgrading these progs (the package is named 'src2pkg-helpers') should rarely be necessary and I'll always notify you when it is. I've added several programs from the coreutils package to the src2pkg-helpers installation which I think will eliminate any possible problems associated with later glibc versions.
I'm going to post a separate announcement of the new version which will contain some other useful information.
Thank you, gnashley:-) I've got two clean installs of Slackware 12.1 at home that I will use your latest src2pkg on:-) I'll report back tonight on how it goes after I return from work.
Heh-heh, I'm glad my annoying post encouraged you to let us use your latest software.
Thanks again for all of the great work you do with supporting the Slackware community:-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.