On Wednesday, March 19, 2025 21:10 CET, Stuart Henderson <s...@spacehopper.org> wrote:
> On 2025/03/19 16:55, Theo Buehler wrote: > > It mostly looks good to me ports-wise, although I'm not at all convinced > > by the devel/bear use case. It feels very expensive for what it provides. > > I guess I'm just not the target audience. That's fine. > > > > Do we really want or need to ship these, especially the systemd one? > > > > lib/cmake/grpc/modules/ > > lib/cmake/grpc/modules/Findc-ares.cmake > > lib/cmake/grpc/modules/Findre2.cmake > > lib/cmake/grpc/modules/Findsystemd.cmake > > I wonder if they might reference each other, maybe I'll take a look > if I remember to do so when it finished building ;) > > > I am really reluctant okaying this just because it is yet another Google > > C++ monster that will significantly add to bulk build times. > > (especially on archs other than amd64/aarch64) > > > I can live > > very well without this and its only prospective consumer. On the other > > hand, nobody's really objected so far... > > Same for me. The other thing with Google C++ monster libraries as far > as I've seen is that they often don't seem to concern themselves too > much with cross-version compatibility, I think they may assume that > the typical downstream user will vendor them. > > > What do others think? Yay or nay? > > > > All that said, if this goes in, I'm ok with importing devel/bear. > > Already some time ago, there were at least one or two ocassions, I would have needed grpc as a dependency, can't rember what those were. If it doesn't go in due to concerns, I'll hopefully remember that thread here ;) Sebastian
