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.
Speaking of tar, has any way been found to work around the symlink issue with pkgtools requiring tar-1.13? Does bsdtar from libarchive clobber symlinks like tar does?
Speaking of tar, has any way been found to work around the symlink issue with pkgtools requiring tar-1.13? Does bsdtar from libarchive clobber symlinks like tar does?
tar has a --dereference flag that may do the trick, but when I asked Pat about it he didn't think it was worth upgrading until tar-1.13 was unable to compile, exact response:
Quote:
> I am curious if tar 1.13 could be replaced by a shell script running:
>
> # tar --dereference
Possibly, but then the package system would be at risk from any new bugs
in future versions of tar. As tar-1.13 is tried and true for our
purposes, I'd rather not go down that road until such time that it
develops too much bitrot to compile on a modern toolchain.
tar has a --dereference flag that may do the trick, but when I asked Pat about it he didn't think it was worth upgrading until tar-1.13 was unable to compile, exact response:
Sounds reasonable. I have been studying how other packagers works and most seem to use libarchive (possibly for bsdtar). Pacman and others use it I think. Interesting...
I'm happy to leave GNU tar 1.13 alone for Pkgtool usage but I do think we should upgrade tar 1.26 to 1.28 as it has some decent fixes. I would also suggest upgrading GNU cpio to 2.12.
I had actually started another thread as I missed (or more likely forgot) about this one. Details of these two updates in that thread.
Speaking of tar, has any way been found to work around the symlink issue with pkgtools requiring tar-1.13? Does bsdtar from libarchive clobber symlinks like tar does?
The newest GNU tar has the the option --keep-directory-symlink. From the manual:
Quote:
This option changes the behavior of tar when it encounters a symlink with the same name as the directory that it is about to extract. By default, in this case tar would first remove the symlink and then proceed extracting the directory.
The `--keep-directory-symlink' option disables this behavior and instructs tar to follow symlinks to directories when extracting from the archive.
It is mainly intended to provide compatibility with the Slackware installation scripts.
But again, for clarity I am still not suggesting that Slackware replace tar 1.13, only that it replaces tar 1.26.
That said, new behaviours and switches such as this are encouraging in case we ever find ourselves in a situation where we have to change. Very nice that the maintainer actually considered Slackware when adding this option
Sounds reasonable. I have been studying how other packagers works and most seem to use libarchive (possibly for bsdtar). Pacman and others use it I think. Interesting...
Pretty sure pacman just uses libarchive directly. It does not care about bsdtar. bsdtar just gets installed on all Arch systems as it is part of the libarchive package.
Still it is handy to know that bsdtar is pre-installed on Arch and Slackware as it is pretty powerful (it can open debs and rpms directly for example).
For compression I am used to lzip, instead of xz. But I prefer the multithreaded version of lzip : plzip .
Why is lzip in slackware, but not plzip ?
Presumably for the same reason many other things are not in Slackware: you can easily install it yourself. It has been clearly stated over and over again that Slackware provides you with a base upon which you can build. It does not provide you with everything out of the box. If you want that then download and install all Debian DVDs instead.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
