Closed echawk closed 1 year ago
why not use kiss l
?
firefox: --enable-default-toolkit=cairo-gtk3-x11-wayland
@wael444 I try to avoid the use of kiss l
since for people who use forks of kiss, yet are kiss compatible, they wouldn't be able to use this repo.
I think this check is fine, however it may be more of a philosophical issue. Since if we were to do that, we could also do this for everything else, not necessarily pretending to wayland vs xorg. I think long term it might become too cumbersome to maintain and test both platforms. So since this is kiss-xorg I would not warrant this change. Let things be separated repos despite the duplication of packages. Coherency.
Like, there is a reason why kiss is primarily x86_64 distro. We could make every package have cross builds for arm (with appropriate checks), but we don't do that, so for the same reason I would not do the wayland check.
Not sure, I don't think new kiss users would enjoy having to fork and maintain the package to have it work for gtk and wayland for the use of xwayland
This is more or less what carbslinux does in its repo. And I belive it works more or less well there.
Is this somewhat in the direction youre pointing to here?
in any case; is this even needed? if users wish to use wayland, they wouldnt be bothering with this repo at all, and if they want to use X, theyd use this. The only usecase that comes to mind would be the transision between X and wayland would possibly be made easier with this.
@kyx0r also brought up a valid point about maintainance getting cumbersome if things get complex.
This is kiss-**xorg**
after all, should we really prioritize wayland?
A similar point was brought up in the s6
discusion aswell.
The details is here
Now, im not entierly against this, if this can be acheived without things breaki, but adding wayland stuff here (with the exception of xwayland perhaps) would break away from the whole point of this repo imo.
This is more or less what carbslinux does in its repo. And I belive it works more or less well there.
Is this somewhat in the direction youre pointing to here?
in any case; is this even needed? if users wish to use wayland, they wouldnt be bothering with this repo at all, and if they want to use X, theyd use this. The only usecase that comes to mind would be the transision between X and wayland would possibly be made easier with this.
Somewhat - it is moreso for people who use wayland but also want access to some X libraries. I think in retrospect, I think it would be suffice to add the check only in
mesa
since I'm ok with making the assumption that any wayland user is using xwayland aswell. Therefore, adding the wayland checks to other X software is totally unnecessary. I'd have to double check if this is the case, but I think it is.@kyx0r also brought up a valid point about maintainance getting cumbersome if things get complex. This is
kiss-**xorg**
after all, should we really prioritize wayland? A similar point was brought up in thes6
discusion aswell. The details is hereNow, im not entierly against this, if this can be acheived without things breaki, but adding wayland stuff here (with the exception of xwayland perhaps) would break away from the whole point of this repo imo.
I think the overall maintenance burden would be pretty minimal, since if we go the route that I just suggested, only one package needs to be maintained.
closing due to the presence of xwayland/
Currently this would only affect the following packages:
The proposed changes are in the following diff: