Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 97:19:06 |
Calls: | 290 |
Files: | 904 |
Messages: | 76,468 |
Hello
The state of GNOME in Gentoo could use a bunch of work and we don't
really have the developers currently to take care of it.
My own grandiose plans to be back and keep things in good order faced
sad reality (a bunch of personal things) and we could really use some
help in at least carefully reviewing and merging a contributors lots of
work, and hopefully more.
While I don't have the time, energy and currently motivation to be
hands-on in the git tree right now, I am online on IRC rather
constantly (lets say while waiting on work rust code compilation ;) and
happy to help on-board an interested developer or developers with any peculiarities (which hopefully would get documented in the process), questions, module interactions, whatever is needed, including during PR reviews, just please do keep in touch, so I can offload things from my
brain for a more sustainable future.
Given a huge stack of available pull requests from a contributor, the
main need right now is someone with a Gentoo developer hat who can help review these and get good things merged, fixed what's needed, and keep
an eye out on the bugs. Of course contributors are welcome too, but
please keep an eye out for not duplicating work that's already waiting review.
To my knowledge, one big issue right now is a circular dep between glib->gobject-introspection->glib, which needs proper solving to move
forward with things. Or at least look at reducing the glib requirement
in gnome-shell some way to at least unleash that core stack for our
users. There are ideas we can talk about.
Chewi was also trying to see if portage can be convinced to stage the
same package twice with different USE flags in the same emerge process
in order to solve cyclical USE flag dependencies, but it's not a
guarantee...
On Wed, Sep 25, 2024 at 02:05:10PM -0400, Eli Schwartz wrote:
Chewi was also trying to see if portage can be convinced to stage the
same package twice with different USE flags in the same emerge process
in order to solve cyclical USE flag dependencies, but it's not a guarantee...
I see it more as giving us hope of being able to remove whatever
horrible hack we implement eventually, but I think the horrible
hack will have to exist in the interim.
On Wed, 2024-09-25 at 14:41 -0400, Ionen Wolkens wrote:
On Wed, Sep 25, 2024 at 02:05:10PM -0400, Eli Schwartz wrote:
Chewi was also trying to see if portage can be convinced to stage the same package twice with different USE flags in the same emerge process
in order to solve cyclical USE flag dependencies, but it's not a guarantee...
I see it more as giving us hope of being able to remove whatever
horrible hack we implement eventually, but I think the horrible
hack will have to exist in the interim.
Yes, the glib/gobject-introspection conflict was my main test case. It was an interesting one because it also involved some blockers. I pushed my half baked
idea up to GitHub in the hope that Zac or someone could maybe take it and actually make it work properly. The results so far have shown that it at least
seems feasible. Once complete, we could get it out the door quite quickly.
As for GNOME, I'm afraid I don't use it, but I do recognise the importance these packages have even on my KDE system, so I am very grateful for Leio's hard work.
Yes, the glib/gobject-introspection conflict was my main test case. It was an interesting one because it also involved some blockers. I pushed my half baked
idea up to GitHub in the hope that Zac or someone could maybe take it and actually make it work properly. The results so far have shown that it at least
seems feasible. Once complete, we could get it out the door quite quickly.
On 9/25/24 1:47 PM, Mart Raudsepp wrote:
Hello[...]
To my knowledge, one big issue right now is a circular dep between
glib->gobject-introspection->glib, which needs proper solving to move
forward with things. Or at least look at reducing the glib requirement
in gnome-shell some way to at least unleash that core stack for our
users. There are ideas we can talk about.
This is... tricky. The obvious possibility is to try to build a
bootstrap copy of AAA inside the ebuild for BBB as a bootstrap thing, as
long as that is sufficient to build a proper copy of AAA using the
partially valid installation of BBB.
Chewi was also trying to see if portage can be convinced to stage the
same package twice with different USE flags in the same emerge process
in order to solve cyclical USE flag dependencies, but it's not a
guarantee...