About auto-forking the Slackware into Jurassic Linux for its beloved 90 old supporters and keeping going for rest of us...
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.
Besides the choices by Design (i.e. our INIT System is BSD like by inception, then it never can be friendly with SystemD), I can't see any serious lack of modernity under (current) Slackware, excluding the LinuxPAM and its Kerberos friend.
Instead, I would like to argue, for example, that P.V. should be more conservatory about GCC, which is so modern that can create possible compilation problems, in my opinion.
Even for those who blame the lack of dependencies, I don't know if is not already know, that Slackware sports a fully functional RPM, and someone who grow a pair of balls, can literally rebuild the Slackware into RPM packages and get his dependencies goodness in a native way, with no additional package.
Then, either our resident Grandpas aren't too efficient in their protests...
OR, much better, as I like to believe, our resident Grandpas are some cool guys, ready to teach lessons of modernity to their nephews.
PS. Only a single example, there, if my memory isn't wrong: a brave French Grandpa, our friend Didier, works to modernize the Slackware installer and make it multi-language.
Last edited by Darth Vader; 02-01-2016 at 11:38 AM.
Besides the choice of compiler version I have also struck by the fact choose the new 4.4 kernel. I guess Patrick has not chosen the 4.1 series because their EOL is Sep 2017 (a little too close in time).
Even for those who blame the lack of dependencies, I don't know if is not already know, that Slackware sports a fully functional RPM, and someone who grow a pair of balls, can literally rebuild the Slackware into RPM packages and get his dependencies goodness in a native way, with no additional package.
PACKAGE NAME: rpm-4.12.0.1-x86_64-1.txz
PACKAGE LOCATION: ./slackware64/ap
PACKAGE SIZE (compressed): 808 K
PACKAGE SIZE (uncompressed): 3720 K
PACKAGE DESCRIPTION:
rpm: rpm (RPM package format tool)
rpm:
rpm: RPM is a tool from Red Hat Software used to install and remove
rpm: packages in the .rpm format. When installing RPM packages on
rpm: Slackware, you may need to use the --nodeps and --force options.
rpm: Before installing any binary package, it's wise to examine it to
rpm: see what it's going to do, and if it will overwrite any files. You
rpm: can use rpm2tgz to convert .rpm packages to .tgz packages so you
rpm: can look them over.
rpm:
Pat takes care of allowing its users to manage RPM packages with rpm tools if they want.
He also wrote scripts to convert these packages from RPM format to standard GNU tar + GNU zip format, so users can use the Slackware tools to manage them (this is recommended).
Just type one of these commands to know their usage:
Code:
rpm2tgz
rpm2txz
rpm2targz
Last edited by Didier Spaier; 02-01-2016 at 02:43 PM.
PACKAGE NAME: rpm-4.12.0.1-x86_64-1.txz
PACKAGE LOCATION: ./slackware64/ap
PACKAGE SIZE (compressed): 808 K
PACKAGE SIZE (uncompressed): 3720 K
PACKAGE DESCRIPTION:
rpm: rpm (RPM package format tool)
rpm:
rpm: RPM is a tool from Red Hat Software used to install and remove
rpm: packages in the .rpm format. When installing RPM packages on
rpm: Slackware, you may need to use the --nodeps and --force options.
rpm: Before installing any binary package, it's wise to examine it to
rpm: see what it's going to do, and if it will overwrite any files. You
rpm: can use rpm2tgz to convert .rpm packages to .tgz packages so you
rpm: can look them over.
rpm:
I am familiar with rpm and rpm2tgz. Darth Vader comment was about rebuilding the whole Slackware system into rpm packages. I didn't hear such a thing before.
I am familiar with rpm and rpm2tgz. Darth Vader comment was about rebuilding the whole Slackware system into rpm packages. I didn't hear such a thing before.
He said it was theoretically possible. Which it is. I don't think he meant it as a serious suggestion
If I remember correctly, he was in the process of converting Darkstar Linux to a RPM based distro when his employer pulled the plug. I also remember that he was not using the actual RPM source but his own forked version.
But, nobody cared enough to preserve the Darkstar sources, or else someone thought there was still monetary value in the work done so far and went private with all of it.
Am I noticing a repeated topic as of recent? "How can someone make Slackware, not Slackware?"
I'd summarize the trend as "lots of trolling", personally. I'd explain it as the wait (and possibly the late inclusion of Pulseaudio) making people restless.
If I remember correctly, he was in the process of converting Darkstar Linux to a RPM based distro when his employer pulled the plug. I also remember that he was not using the actual RPM source but his own forked version.
Well, DPM is not RPM based. It is suite of package management, written in C++, not C. Practically, under top-end, something able to use repositories. Using a very own script, package and repository format, dependencies and able to compute dependencies from repositories. A very un-Slackware tool, probably with no interest for this community, anyway...
Quote:
Originally Posted by Alien Bob
But, nobody cared enough to preserve the Darkstar sources, or else someone thought there was still monetary value in the work done so far and went private with all of it.
Eric, considered that part of those sources was public available even into KDE-APPS, what you suppose for me to do as plus?
Finally, I even tried to promote a Package Builder, specially written to generate Slackware packages using specs similar to rpmbuild, right there, in this forum.
Everything developed by DARKSTAR was for years in your hands, why you, guys, do not have a copy, for example, of the applications, which are much more smaller than the distribution, sine die?
Last edited by Darth Vader; 02-01-2016 at 05:18 PM.
EDIT: The wayback machine appears to just save the directory links but none of the contents of the files. It's difficult to think of a more useless exercise.
Last edited by Richard Cranium; 02-02-2016 at 08:55 AM.
Reason: Link was worthless.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
could it be that there is a clash of 'sense of humor' somewhere hidden in this thread 
