1 |
On Sun, Jul 03, 2022 at 09:03:04PM -0700, Georgy Yakovlev wrote: |
2 |
> I've been rather busy lately and can't keep up with all of my packages. |
3 |
> There are pending bumps, some bugs, but nothing too crazy or hard. |
4 |
> So I'm looking for someone to co-maintain (or even take over if you |
5 |
> insist) the following packages: |
6 |
> |
7 |
> * dev-cpp/abseil-cpp |
8 |
> Googleware, it's usually bundled into source, like gnulib, but some |
9 |
> projects use system copy. |
10 |
> Hardcoded flags, broken abi every other bump, may require slotting in |
11 |
> the future, some revdeps rely on older versions. Not hard to maintain, |
12 |
> but has more that usual blast radius. |
13 |
|
14 |
I'll take this, I already end up having to apply random patches to make |
15 |
it play well with CUDA. |
16 |
> |
17 |
> * net-libs/grpc |
18 |
> * dev-python/grpcio |
19 |
> * dev-python/grpcio-tools |
20 |
> * dev-python/grpcio-testing |
21 |
> grpc stack, googleware again. rather frequent releases, lack of |
22 |
> portage-able tests, as tests insist on downloading gtest stack git |
23 |
> master in src_test phase. |
24 |
> Technically it's already co-maintained, but I't be beneficial if we |
25 |
> have more hands and eyes on this one. |
26 |
> python project has been helping with python packages, but lack of tests |
27 |
> makes the package somewhat risky. |
28 |
> bonus points if you can test it with tensorflow. |
29 |
|
30 |
I'm the co-maintainer on this already but as Georgy said, happy to have |
31 |
other maintainers as well, I dont really interact with it other than via |
32 |
TensorFlow. If people use it as deps from other things that would be |
33 |
great too :) |
34 |
|
35 |
-- Jason |