dmbtech wrote:Well, I kind of feel thats inconveient, and kind of overkill. Like, lets say your a developer, you just want to get this small program installed where there is not ebuild. It would take up way to much time to create an ebuild for it and then store it in an overlay. There should just be a way to do run a program after compiling, which wraps make install and maybe perhaps creates the ebuild and installs the ebuild for you.
A basic ebuild that just wraps configure, make, make install, is really small and doesn't take much space at all.
I would compare checkinstall install more with quickpkg which takes the installed program and creates a binary backup, very much like the RPMs checkinstall creates.
Although you might think this is good, the majority of us want to keep packages installed out of portage to a minimum.
Keeping everything in portage has a tremendous upside.
Once you create a basic template ebuild, it takes nothing to rename it and copy it into your overlay. You could even write a BASH script that asks for the name and category in portage, edit the template, then do everything you asked, (move to overlay, emerge, etc), with only a few lines of code.