[Slackbuilds-users] sip conflicts with kdeaddon

Patrick J. Volkerding volkerdi at slackware.com
Sun Mar 9 05:21:21 EDT 2008

ciol wrote:
> Aleksandar B. Samardzic wrote:
>> There is a slight issue with conformance this way - having files from
>> a package installed into /usr/local would be against LSB, and also,
>> more importantly, against long standing Unix tradition to only have
>> software compiled locally, from the source, installed there...
> Slackbuilds from SBO belong to this tradition (in my opinion), but I do 
> not want to speak about this again.

IMO, a package built from a proper SlackBuild should not be putting 
files in /usr/local.  They are manageable packages that _could_ be 
deployed on multiple systems, and even if they aren't it's a little 
different than using "make install".

The correct solution (I think) would be for python to have a 
vendor-python directory much like perl's vendor_perl that we've started 
to use.  But there are other overlaps here, too.

> Anyway, why not create a /usr/slackbuilds-conflicts for these kind of 
> conflicting packages?

What a terrible name.  Perhaps suggest that to the LSB as an offical 
directory under /usr?  ;-)

Perhaps /opt would be a better choice.  You can decide how to arrange 
your $PATH.

My $0.02.


More information about the Slackbuilds-users mailing list