You are not logged in.
After setting up a new Arch install on a new computer, I found that if I installed Xorg and chose libglvnd it also ended up installing Wayland as it's a dependancy of mesa.
Is this meant to happen as if not I would much rather not take up space on my hard drive with another display server and if so, is there any way of me not installing it without pacman reinstalling it every time there is an update.
Thanks in advance for any help.
Last edited by dancan12345 (2017-04-07 07:48:31)
Offline
You could add its files to the NoExtract directives. however this might lead to all sorts of subtle breakage with packages that link against it. Also Wayland isn't a display server, it's a protocol to implement one. It takes up a grand total of 714.8KB of diskspace you are going to have a lot more and bigger problems if that amount of diskspace isn't something you can spare.
Offline
Oh okay, I just thought it was a litle odd that I should have to install both.
Thanks.
Offline
Wayland is a library. Many packages have a hard dependency on it, even when you use Xorg, so not install it won't be easy. But that doesn't mean Wayland will effectively be used nor that any server or other "wayland things" will run on your computer.
If you really don't want it to be present on your hard disk, you will have to recompile any package that depends on it passing the option not to use it. As Archlinux is a binary distribution, this would not really be manageable and would somehow amount to fork Archlinux. Gentoo, being a source-based distribution supports such kind of things.
But do you really want that? Wayland takes only 700Kb of space, less than 1Mb! I can't imagine such tiny difference does really matter.
Offline
Yeah I think I will just install both rather then recompiling everything, I just didn't realise it was that small.
Offline
If you really want to get rid of wayland support, AUR does have a mesa-nowayland package .
The maintainer doesn't seem to update it often though .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
@Lone_Wolf maybe. But you need also a version of gtk3 without wayland. It is unlikely not to need gtk3 nowadays. But then again I see a package on the AUR. Right you do not have to recompile everything, but I don't think it is worth the hassle.
Offline