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.
This is a great little app, works flawlessly but for a minor detail, at the end when the .tgz is placed in /tmp and i try to install it with 'installpkg' as root, and put the first 3-4 letters of the app to be installed and press TAB to autocomplete the name it just does part of it. I have to enter the rest manually, otherwise, it gives an error saying the app does not end in .tgz when in reality it does. Is this small bug? Thanks.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
src2pkg
This is a great little app, works flawlessly but for a minor detail, at the end when the .tgz is placed in /tmp and i try to install it with 'installpkg' as root, and put the first 3-4 letters of the app to be installed and press TAB to autocomplete the name it just does part of it. I have to enter the rest manually, otherwise, it gives an error saying the app does not end in .tgz when in reality it does. Is this small bug? Thanks.
Sounds like what you seeing is Bash shell behavior and nothing to do with src2pkg. It may well be that the package has been built in the /tmp directory in a sundirectory named after the package's basename so there is more than one directory entry matching.
What happens if you hit tab twice after keying in the start characters ?
Another way may be, for example, if the package is created at /tmp/tunctl-1.5-i486-1_SBo.tgz, would be to run as root "installpkg /tmp/tunctl*.tgz" and let the shell glob the results.
Sorry if this is way off the mark - just some ideas !!
mRgOBLIN and bgeddy are right on the mark. By default, src2pkg creates temporary working directories unser /tmp and also leaves the finished package there -the same way that a SlackBuild would do it by default. And the name of temp dirs created for the sources and package tree both start the same as the finished package.
Using the foo-1.2.3 example, the sources are in /tmp/foo-1.2.3-src-1, the package tree is in /tmp/foo-1.2.3-pkg-1 and the package, of course, would be /tmp/foo-1.2.3-i486-1.tgz
'installpkg /tmp/foo*.tgz' should work.
For convenience, you might want to change the setting for PKG_DEST_DIR in your /etc/src2pkg/src2pkg.conf file to this:
PKG_DEST_DIR=$CWD
That will always place the finished package in the same directory where you run src2pkg from. (There is already such a line in the conf file -you can simply uncomment it)
mRgOBLIN and bgeddy are right on the mark. By default, src2pkg creates temporary working directories unser /tmp and also leaves the finished package there -the same way that a SlackBuild would do it by default. And the name of temp dirs created for the sources and package tree both start the same as the finished package.
Using the foo-1.2.3 example, the sources are in /tmp/foo-1.2.3-src-1, the package tree is in /tmp/foo-1.2.3-pkg-1 and the package, of course, would be /tmp/foo-1.2.3-i486-1.tgz
'installpkg /tmp/foo*.tgz' should work.
For convenience, you might want to change the setting for PKG_DEST_DIR in your /etc/src2pkg/src2pkg.conf file to this:
PKG_DEST_DIR=$CWD
That will always place the finished package in the same directory where you run src2pkg from. (There is already such a line in the conf file -you can simply uncomment it)
Does this need to be updated in the WiKi?
Compatibility with Slackware versions
src2pkg has been tested and works with the stable releases of Slackware 11.0 and 12.0.
I have not tried this yet but might give it a shot.
Ummm, I don't think it needs to be updated in the wiki -I mean the default behaviour has been the same for quite a long while now. You can also override the PKG_DEST_DIR from the command line by using the '-C' option with src2pkg or by running it like this:
PKG_DEST_DIR=/path/to/dir src2pkg OPTIONS tarball-name
In the case of the current dir you could use:
PKG_DEST_DIR=$(pwd) src2pkg OPTIONS tarball-name
to do the same thing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.