|
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. |
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).
|
Quote:
|
:confused: could it be that there is a clash of 'sense of humor' somewhere hidden in this thread :confused:
|
Quote:
|
Quote:
Code:
PACKAGE NAME: rpm-4.12.0.1-x86_64-1.txz |
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 |
Quote:
|
Quote:
|
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?"
|
Quote:
|
Quote:
Quote:
http://kde-apps.org/content/show.php...?content=56982 http://kde-apps.org/content/show.php...?content=70149 http://kde-apps.org/content/show.php...?content=70150 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. https://www.linuxquestions.org/quest...-linux-810053/ 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? |
Useless url deleted
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. |
All times are GMT -5. The time now is 09:32 AM. |