| |||||||||||||
Slackware 14 releasedSlackware 14 releasedPosted Oct 1, 2012 17:19 UTC (Mon) by dlang (✭ supporter ✭, #313)In reply to: Slackware 14 released by dark Parent article: Slackware 14 released
no, it doesn't mean untested.
It also doesn't mean _no_ distro patches, but they try really hard to avoid them.
One of the biggest things that it means is that the package gets installed where the developer configured it to be installed. You won't ever see a discussion about merging /bin and /usr/bin on slackware, for the simple fact that slackware doesn't overrride the decision from the upstream package as to where it wants to be installed.
(Log in to post comments)
Slackware 14 released Posted Oct 2, 2012 20:02 UTC (Tue) by mgedmin (subscriber, #34497) [Link]
Don't packages usually install into /usr/local, when you do ./configure && make && sudo make install? I haven't used Slackware since 1998, but IIRC it kept most stuff in /usr/bin, not /usr/local/bin.
Slackware 14 released Posted Oct 2, 2012 20:50 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link]
picking compile time options is not patching the software.
some software compiles into local, some doesn't. It varies from package to package.
Slackware 14 released Posted Oct 7, 2012 19:40 UTC (Sun) by bersl2 (subscriber, #34928) [Link]
I actually don't recall any official Slackware packages installing into /usr/local for quite some time (aaa_base notwithstanding). In fact, most patches applied in the official SlackBuilds seems to be related to install paths of various sorts sometimes not being configurable except by changing a file.
|
|||||||||||||