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