I’ve made version 0.2 available of cvechecker. It fixes some build warnings and also supports the normal “make install” step. The pullcves command now also pulls in the latest versions.dat file. Special thanks to Per Andersson for reporting that the ./configure didn’t fail if sqlite3 or libconfig wasn’t available – that should be fixed now as well.
In my Gentoo overlay, cvechecker-0.2.ebuild has been put available. Thanks there to webkiller71 for helping out with a more sane approach to cvechecker-0.1.ebuild – I hope I didn’t screw up his changes in 0.2 too much ;-)
You’re welcome for the cleanups. I also noticed that libconfig was needed and added it to DEPEND. There’s a patch to also add the correct version number in my github clone. About 0.2: if you don’t use dodir, diropts is useless and can be removed. Also, adding || die to chgrp and chown might be a good addition (same patch in my github clone).
In your SVN source tree you could remove some autogenerated files and add them to svn:ignore so they never end up in SVN. This would be config.h, config.h.in, configure and Makefile.in. When you’re making a tarball, you should generate the files once and distribute them. In your ebuild you can inherit autotools and have src_prepare() { eautoreconf } to generate them if you do have a live ebuild (which I just added to my github clone and includes eautoreconf).
Last, but not least I should tell you that I know very little about auto*, but you could consider adding parameters to mkinstalldirs in Makefile.am (the same as diropts accepts, see man install) so you’re fixing the permissions in the make install step instead of afterwards. Also, having a cvechecker.conf.in and generate cvechecker.conf with the ./configure values might be nicer as well, but once again, that’s beyond my auto* skills. It’s just nice to have, but it’ll reduce your ebuild to a minimum and also make installation easier for non-ebuild users like LFS-users.