On 2016-01-22 11:51, Ian Stakenvicius wrote: > The eclasses look good to go for me -- i've built an ebuild for pl/R > using them and it works as expected (and it's nice to not have to > define PG_CONFIG et. al. myself too). > > Can the eclasses be migrated to the tree soon?
I wanted to test the eclass against pgTAP as well with the default functions, but have been struggling the past couple days with getting my machine up to date. I would like some feedback on the documentation/comments in the eclass. I'm certain it could be improved. Though, if you were able to follow them (not a slight, just you were the first to follow them), I might have done good enough. > Also of note, it will be important to stabilize soon the ~arch > versions of postgresql that have the install_bin path patched; > otherwise if portage is, say, reinstalled with a different python > selection between when postgres is emerged and one of these new > postgres-multi packages are emerged, installation fails. Oh, yes, I think we can move towards stabilization as soon as my Internet is back up.
signature.asc
Description: Digital signature
