Re: Removal from Slackware 12 ??

[tmhikaru@xxxxxxxxx]

On Thu, Aug 02, 2007 at 10:56:44PM -0500, Lawrence Toal wrote:
> Aw, that's disappointing--can you shed some light on this?  Posters on AOLS 
> seem divided on weather or not version 1.6.1 works, or maybe 1.5.1
> works better.  Some say the "--fstrans=no" option solves their problems.  
> Unfortunately,  some  shed more heat than light on such things.  I'm 
> guessing the checkinstall list has the straight story.

Fellow slack 12 user here; the problem is with the library checkinstall uses
as a wrapper - you'll see checkinstall make install fail when any install
tries to use chmod. It has something to do with something that coreutils
changed in slack 12... I don't have much more information, however I *DO*
know how to workaround it by using the checkinstall package from slackware
11:

In the config file:
Do not strip libs or binaries, do not compress manpages, do reset uids to
root:root, do install the package... When using it, do not create a doc-pak
directory as it suggests.

Now for how to make this work. 90% of the time you'll still be able to get
away with checkinstall make install; on those few occasions where this fails
due to chmod, instead do:

make install && checkinstall make install

- it'll wind up installing the stuff *TWICE* - but on the other hand, you'll
  still wind up with a package you can use to remove it later.

Definitely not perfect as when checkinstall installs the package files the
permissions will be changed to the ones checkinstall sets, so this may break
some special apps that require perms to NOT be root:root, but seems to work
otherwise for me here.

Hikaru