What?! I thought it was unbreakable. I had a C programming assignment once and wrote some faulty code. This code ran perfectly on Slackware, but not when I compiled it on any other system. I only tested it on Slackware so I didn't notice, but the teacher was running Ubuntu so he complained immediately. I discovered it too when I tested it on Debian. A "rational" person would probably say that it was because of the GCC version difference or configure settings, but I know better... it is the paranormal power of Slack.
Quote:
Originally Posted by WhiteWolf1776
And to add to my friend hitest's post... be sure you setup the /etc/slackpkg/blacklist file prior to running that 'clean-system' command...
|
It can also be used for blacklisting KDE packages that you don't want to see in 'install-new', if you didn't install KDE.
By the way, another way of identifying a Slackware package is 'tar -tf <file>.tgz'. In a Slackware package you will see FHS install paths, like:
Code:
/usr/bin/...
/usr/doc/...
/usr/man/...
There is also an 'install' directory containing (at least) a 'slack-desc'.