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.
Yes, I'm sure my scripts are not the only ones that take advantage of that particular pattern. .tzz would work while maintaining the status quo.
I can work-around anything you decide to go with, but if you can let us know one way or the other then those of us who write package related tools can get ahead of the game should you decide to switch.
I patched pkgtools and slackpkg (and gen_repo_files.sh) to use .tzz extension about 12 months ago. It works perfectly. Creating and installing package is very fast, I enjoy a lot!
I am not hung up on three character "extensions" that have no real meaning or purpose in Linux anyway.
Unlike other distros, Slackware packages don't have a specific suffix. The 3 character (dos style) .t[gbxl]z suffix fills that roll, helping differentiate a normal source tarball from a package tarball. CRUX use .pkg.tar.xz which I'd argue is better, but we're dealing with 30 years of history/continuity. It's not ideal, but it's where we are.
It is urgent not to change anything in the package manager
time tar -cvf archive-lvl6.xz -I 'xz -6' /usr/src/linux-5.4.272-test01/
real 9m5,413s 192.0 Mo
time tar -cvf archive-lvl6.lz -I 'lzip -6' /usr/src/linux-5.4.272-test01/
real 9m35,764s 195.2 Mo
time tar -xf /home/archive-lvl6.xz
real 0m34,407s
time tar -xf /home/archive-lvl6.lz
real 0m42,871s
I think the speed balance is important. It can take time to make an archive, but they're quick to decompress. They're only made once. How many times are they opened?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
