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.
Distribution: Slackware 10.2 kernel 2.6.13, Gentoo amd64, Some mish-mash of programs that started with slack 9.0
Posts: 165
Rep:
If I understand your question this is what you have to do.
installpkg installs precompiled binaries into the directorys given to it during "configure". In an "offical" Slackpackage this is determined in the SlackBuild script. Usually the executibles go to /usr/bin, the library files to /usr/lib, documentation to /usr/doc, etc.
To change this, for example you want everything to go to the /usr/local tree, it needs to be specified by editing the .SlackBuild script then recompiling the source with that script.
If you want to make the package your self use a prefix flag when running configure. Such as ./configure --prefix=/usr/local, then run make, then checkinstall.
Right... Theres no way to install it somewhere else. cd into an empty folder and 'tar -xzvf blah.tgz' and you'll see where it is going to put everything. Moving stuff around to your liking and then repackaging with makepkg isn't going to work 9 times out of 10 either cause your binaries and libs are hard wired to a specific location. Grabbing the source and specifying a './configure --prefix=/someplace && make && make install DESTDIR=/EmptyFolder && cd /into/EmptyFolder && makepkg NewBlah.tgz' is the only way to go about it.....
You can install to a system 'remotely' by using the install CD. Mount your desired target on /mnt, then run pkgtool. This is also the safest way to upgrade.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.