We share the same philosophy, and the addition of the checkinstall program makes creating a slackware package even easier, however it seems
I tried out checkinstall once upon a time... but I stopped using it.
The reason was that if something went wrong with a checkinstall process, you're going to have to peer under the hood and understand what checkinstall did and why it did it wrong. I don't want to invest additional time understanding how checkinstall works behind the scenes and frankly the pure pkgtools way is not really all that tedious and has the added benefit of being a very lucid process.
Furthermore, problems when building packages are invariably due to autoconf mumbojumbo anyway and completely unrelated to the packaging tools, thus, checkinstall is of zero help in such cases.
Any package that does not obey
make install prefix=/pkg-creation-directory
and puts even a single file elsewhere needs to have its build system fixed. With all the dozens and dozens of packages I've built from tar.gz's, only SWI-Prolog (and omniORB I think) had this problem and the files that went to an outside directory were easily tracked down (by keeping a close eye on the make output) and transferred to the package creation directory.
I dunno, perhaps if one day I felt I understood exactly what checkinstall does underneath, maybe I'll use it, but I'm kind of doubtful about that.
Just my two cents, YMMV...
-- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
