dev-cpp/gflags-1.3 was released on 2010-01-04.
It looks like they split up the python bits; so I am working on a ebuild for those separately. -A
Created attachment 229179 [details] Split python bits into dev-python/python-gflags-1.3.ebuild Arfrever, can you take a look at this ebuild to make sure I'm not doing anything crazy?
Created attachment 229181 [details] use $(PYTHON)
You should use distutils.eclass and not define any phase functions explicitly. Please set PYTHON_MODNAME variable (in global scope) with paths (relative to site-packages directories), which should be passed to python_mod_optimize() and python_mod_cleanup().
Also please set SUPPORT_PYTHON_ABIS="1" before inherit() to support installation for multiple Python ABIs. Maybe dev-python/python-gflags should depend on dev-cpp/gflags.
I've taken over maintaining gflags. Done: - dev-cpp/gflags-1.4 added to portage - dev-python/python-gflags-1.4 - new package, upstream has split off Python library to separate package.