-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xwayland should be moved to extra/ or xorg/ #89
Comments
I'm glad someone has tested it - I havent had the time to. Was the setup roughly the same as on X? Were there any wayland specific things that you had to do? I'd definitely like to offer it as an option, so having some docs on how to set it up would be a first step IMO. |
depends on the compositor, had to fork almost all of them just to have xwayland built in
many packages had to be built both FOR wayland and xorg |
If you had to fork so many packages, would it make sense to ship these forked pkgs in their own repo, maybe |
No. i had to recompile so that programs can run Wayland natively. xwayland should have its own repository, yes; with all of the libraries baked in for Wayland usersand have a xwayland in xorg/ for people like me, who want to use both at the same time |
i will start trying working on this. |
i will NOT start working on this and suggest @ehawkvu to instead push the xwayland repository to many propietary or X applications will still need X libraries. so a user is suggested to use the entire |
plz move it to xorg already @ehawkvu |
done. |
thx |
i have tested xwayland and i believe it should exit testing, and be put in either extra/ or xorg/.
it can also be safely switched out for muon for #86, and wayland users might want this package.
The text was updated successfully, but these errors were encountered: