Q. Kconfigure successfully builds a package (using checkinstall) but does not actually install it. What is wrong?
A. If you are running kconfigure and using version 1.6beta or greater, checkinstall might not automatically install the package it creates. Instead it will build the package and place it in the standard build directory of that distribution. If you want kconfigure to install the package that checkinstall creates do this:
In the kconfigure window Click on Settings and then choose "Configure Kconfigure", Click on the Check Install preference dialog, and in the box marked "Custom Options:" put this in the text box:
and you should be fine. I know this works on (for example) Suse 9.2 ;-)
Q. Checkinstall sometimes fails to create my package even though make install works fine.
A. Ya, checkinstall is far from a perfect replacement for make install. It often works great, but not always. If you have successfully done a make install you can try running checkinstall again (immediately after a successful make install). Sometimes checkinstall will work AFTER make install has installed the files, and will then register the files installed. In the future we may even set it up so checkinstall run make install if it fails the first time and then run itself again.
Q. I liked kconfigure 1.2 better than the new 2.0 series. Any chance you will support the old one?
A. Ahhh... No. The old code-base is so different from the new one it would be like managing two different projects. In addition version 1.2 was strictly a developers tool. Kconfigure 2.0 sets the groundwork for a much more "user friendly" interface. Future versions will include an auto-setup wizard, pre-configured build templates, and simplified install wizard. We would like kconfigure to be as easy to use as Install Shield, but still have the flexibility to be functional for application developers.
Q. Is there a way to have Kconfigure put my checkinstall built packages in some other location than x?
A. Yes and no. Neither checkinstall, nor Kconfigure determines where the built packages are put after they get built. This is handled by the packaging system itself (RPM, SLK, DPKG.) For RPM packages you CAN, however, change the default location for package dumps by doing this:
As root make a new file in /root called .rpmmacros and add this like (replacing the path with your desired path):
If you know how to set this location for other package systems. Please let me know.