Differences installing fuse with checkinstall and with make

crisostomo_enrico · 06-19-2007, 03:20 AM

Hi guys.

I was making a fuse package (v. 2.6.5) for my slackware-current and I installed it in a temp directory with make DESTDIR=/mydir install.

I noticed that make install creates, amongst others:
dev/fuse
etc/init.d/fuse

/dev/fuse already exists (in devs-2.3.1-noarch-25) and, after reading through /etc/init.d/fuse, I think this file isn't needed.

BTW, I tried a checkinstall and noticed that neither dev/fuse nor etc/init.d/fuse were included in the package. Moreover, doinst.sh created by checkinstall includes:
( cd etc ; rm -rf init.d )
( cd etc ; ln -sf rc.d/init.d init.d )
So, every file included in init.d would be deleted!

Can someone explain me checkinstall behaviour?

Thanks,
Enrico,

tramni1980 · 06-19-2007, 03:54 AM

I recommend you to use the slackbuild script from slackbuilds.org:
http://www.slackbuilds.org/repository/system/fuse/
It works great.

crisostomo_enrico · 06-20-2007, 02:45 AM

Thanks, tramni1980, maybe I was a bit imprecise. I usually write a slackbuild file or use someone else's: in the case of fuse, I always used Alien Bob's slackbuild which, correctly, moves /etc/init.d/fuse into /etc/rc.d and starts it up in rc.local. What I do not understand is checkinstall behaviour: it doesn't include that file in the package, as if it was filtering it or the entire /etc/init.d!

Thx,
Enrico.

tramni1980 · 06-20-2007, 06:22 AM

You should probably consult the documentation or the developers of checkinstall about that. For building from source when no slackbuild script is available I use gnashley's src2pkg or trackinstall. src2pkg works better than checkinstall as it is designed specifically for Slackware. You can find src2pkg here:
http://distro.ibiblio.org/pub/linux/...1.3-i486-1.tgz