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 have a few questions, First an overview; I have installed CLFS 64, and have everything basic. I have all runlevel init's installed and have the dhcp up and running.
I have installed pkgtools. I have never used Slackware's pkgtools before so I have a few questions.
1- When ever I install a package with "installpkg" I get this error:
Code:
WARNING: pkgtools are unstable with tar > 1.13.
You should provide a "tar-1.13" in your $PATH.
2 - Is Slackware64 FHS compliant with the /lib directories. Meaning is Slackware64 have a /lib or a /lib64...? And if so, would a sym link work.
3 - How can I install a Slackware groups (i.e. a, ap, e, n, etc...)...? If possible...
I wanna get X installed and a few other apps using pkgtools. And I am a complete novice with Slackware package management.
1- When ever I install a package with "installpkg" I get this error:
Code:
WARNING: pkgtools are unstable with tar > 1.13.
You should provide a "tar-1.13" in your $PATH.
Upgrade tar manually from sources, if pkgtools are not working for You.
Quote:
Originally Posted by manwithaplan
2 - Is Slackware64 FHS compliant with the /lib directories. Meaning is Slackware64 have a /lib or a /lib64...? And if so, would a sym link work.
Slackware64 is multilib OS, and those directories have different meanings - in /usr/lib are 32-bit compatibility libraries, and lib64 is for 64-bit libraries. This is for coexistence of the same libraries compiled with different achitecture.
Quote:
Originally Posted by manwithaplan
3 - How can I install a Slackware groups (i.e. a, ap, e, n, etc...)...? If possible...
Your error gives you the answer, you need a tar-1.13 executable in /bin, once you have done this pkgtools should work and you will be able to use installpkg.
Your error gives you the answer, you need a tar-1.13 executable in /bin, once you have done this pkgtools should work and you will be able to use installpkg.
samac
Ya .. I do have a tar-1.13 in my /bin ... This is why I am confused about this error. I even looked and edited installpkg, still no luck.
I had this problem a while back. My recollection is that it was looking for a link/reference to tar 13, which was fixed with a symbolic link alias; I'm using tar 1.16.1. Sorry I can't give you any more than that. My memory fails me.
Last edited by fourcs; 10-01-2009 at 12:21 PM.
Reason: more info
It doesn't work to use an alias or link. The pkgtools explicitly test the version of tar using 'tar --version'. And they are not kidding about other versions of tar not being supported -tar-1.13 has some specific beahviours which affect the way packages get constructed and installed. And some of the tar-1.13 options called by pkgtools have completely different behaviour with later versions of tar. I strongly recommend that you build tar from the official slackware sources so that tar-1.13 gets properly installed.
Using any other version of tar can cause corrupted database files when installing packages. This means that when you try to uninstall a package, the files don't really get removed at all.
It doesn't work to use an alias or link. The pkgtools explicitly test the version of tar using 'tar --version'. And they are not kidding about other versions of tar not being supported -tar-1.13 has some specific beahviours which affect the way packages get constructed and installed. And some of the tar-1.13 options called by pkgtools have completely different behaviour with later versions of tar. I strongly recommend that you build tar from the official slackware sources so that tar-1.13 gets properly installed.
Using any other version of tar can cause corrupted database files when installing packages. This means that when you try to uninstall a package, the files don't really get removed at all.
Thanks, for the explanation, I was using the official gnu release 1.22, I'll grab the Slack source and compile & test.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
Originally Posted by manwithaplan View Post
3 - How can I install a Slackware groups (i.e. a, ap, e, n, etc...)...? If possible...
You can do this with one of the more obscure options of pkgtool that is the "-sets" parameter. Here is a little script to illustrate this, This will install the t and y sets as if they where selected from the setup asking for optional files and automatically installing required ones. It does this by following the tagfiles on the install disk image :
Code:
#!/bin/bash
MT=$(mktemp -d -t) # create a temporary directory for the mount point
# lets say we have the slackware-13 iso saved in the /tmp directory
mount /tmp/slackware-13.0-install-dvd.iso $MT -o loop # mount slack to mount point via loop device
pkgtool -sets T#Y -source_mounted -source_dir $MT/slackware # use pkgtool for slackware sets t and y
umount $MT # get rid of mounted slackware iso
rmdir $MT # get rid of mount point directory
This should illustrate ways of using pkgtool to install package sets following the included tagfile. You can do all this with installpkg using the "-menu" and "-priority " flags but pkgtool does it all for you.
You can do this with one of the more obscure options of pkgtool that is the "-sets" parameter. Here is a little script to illustrate this, This will install the t and y sets as if they where selected from the setup asking for optional files and automatically installing required ones. It does this by following the tagfiles on the install disk image :
This should illustrate ways of using pkgtool to install package sets following the included tagfile. You can do all this with installpkg using the "-menu" and "-priority " flags but pkgtool does it all for you.
This is a great answer to my post. I was looking for a way to install the sets. Thanks
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.