rickh is completely wrong. Checkinstall is great. It's worked just fine with dpkg everytime I've used it. As DeanLinkous said, you just need to know what argument to put in. If you watch the output as checkinstall installs the program, it will give you the string you need to uninstall it again.
Checkinstall doesn't need to know anything about the "file heirarchy system" or whatnot. All it really does is create a file tracker (in .deb package form, in this case) for wherever "make install" would normally place the files anyway, so that you can easily remove them again when you need to. That's its whole purpose after all, to make source-based installs and uninstalls easier. And dpkg handles packages made by it just fine because all it does is install and uninstall the files as they are listed in the package.
Oh, and it's also not true that dpkg doesn't install the packages made by it. If you watch the output carefully when you run checkinstall that's exactly what it does--it invokes dpkg to install the package it makes. In fact, if you happen to have synaptic or something that uses apt/dpkg open while you're using it, the final install will fail because dpkg is "in use", and you'll have to install the package manually instead.
Edit: Gotta mention one more thing. I just checked the man page, and it looks like you can use the "--pkgname=[name]" flag to create an easier-to-use package name if you have trouble remembering the ones checkinstall normally creates.
Last edited by David the H.; 06-04-2006 at 02:32 PM.