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.
After being on vacation for a couple of weeks I've gotten a new version of src2pkg uploaded which takes care of a couple of well-reported bugs and adds a minor feature or two.
All users who are currently working with src2pkg should upgrade to this version to avoid the bugs still in the last version. Unfortunately there have been lots of minor bugs in the last few versions since I changed so much code. I apologize for the inconvenience and am trying to get everything stabilized again before version 2.0 which should be very stable and well-documented.
Note that I've dropped the option to compile during installation the libs and programs used by src2pkg. You'll need to first run 'src2pkg --setup' as user 'root' after installing or upgrading in order to use it. While the option to run --setup during installation seemed like a good idea, I think it is kind of 'unSlackish'. if you really like it the way it was, let me know about it. If enough people complain I might change it back...
Please continue to report any more bugs you find as I need to get them all worked out over the next few minor versions. Thanks to all who reported bugs, made suggestions or helped with answering questions while I was away.
I don't use '-W' by default in order to encourage you to examine your package tree before deciding that the build was truly successful. Having all temp files cleaned up by default would encourage many folks to proceed to quickly, I think. You can set it as a default for yourself by putting this line in your /etc/src2pkg/src2pkg.conf file:
! [[ $CLEANUP ]] && [[ $CLEANUP = "ALL" ]]
But this means that your sources and temporary package-tree will always be removed unless you do something like this to run your builds:
CLEANUP="" ; sh ./*.src2pkg
or:
CLEANUP="" ; src2pkg -X
or:
CLEANUP="" ; src2pkg tarball-name
This is beacuse I've not built in an easy way to switch it on *and* off, just an easy way to switch it on, since it is off by default.
As for the '-C' option, just uncomment this line in your src2pkg.conf file:
! [[ $PKG_DEST_DIR ]] && PKG_DEST_DIR="$CWD"
I used to deliver src2pkg with everything set to work in the CWD by default -thats the way I use it myself -it makes it easier to examine the package tree or do a quick experiment in the sources. But, I changed everything to work in /tmp by default as a safety measure and to be more 'slackish' about the whole matter. Using the CWD is inherently dangerous if you do something stupid like try to unpack and build stuff under /usr/share or something like that. I actually had a user report doing this a long time ago -I had to build in lots of checks for really weird usage and set saner defaults because I *never* want to hear that some silly user mistake has hosed their system. See the notes about how I set up the working directories in the conf file. If you'll be smart and alway use a separate directory for each build, in a safe place where you have wriet priviledges, then using CWD for everything makes it a lot easier to keep tabs on your packages and sources even while thea are being built.
Coming soon... I've made quite a few changes and have been doing a lot of testing -recently added over 100 packages to my collection -that brings me to over 1000! A few changes you'll be particularly glad to see. Also, work has started(barely) on a wiki for src2pkg.
Coming soon... I've made quite a few changes and have been doing a lot of testing -recently added over 100 packages to my collection -that brings me to over 1000! A few changes you'll be particularly glad to see. Also, work has started(barely) on a wiki for src2pkg.
Since I likely use src2pkg more than anyone besides you, I think I'm in a good position to assist in writing the Wiki pages. Especially since I come across more issues than most will likely encounter. But just saying, I think I could help out there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.