I dont really know much about pipewire. I have been using it through xdg-desktop-portal-wlr, which makes screensharing with WebRTC possible thought Firefox and more. See their wiki. But havn’t touched pipewire myself. We should propably also include xdg-desktop-portal-wlr and the environment varibles needed for that. Then we will ge pipewire anyway 
1 Like
Thats nice to know. I mean of they use it it must be of use
There’s some garda guys here right
Why why now!!! 
❯ sway
[1] 9450 segmentation fault (core dumped) sway
Reproducible anyone? I’ve updated too
LightDM is working! We just need to enable it with systemctl enable lightdm in the script
2 Likes
Beautiful!!
Imma go work on gtk2 and gkt3 and possible gkt4
Try to take a look at the Manjaro settings config. The create the dynamically, but we should just start with hardcoding the values.
1 Like
not needed for installing it with the ISO it handles this automatically if lightdm is installed.
Another question:
is yad working under wayland? or does it needs a tweak to startup?
All the Eos apps (p.e. welcome) are using yad for the interface.
Particular parts of yad won’t work under wayland. It just means we need to write a environment variable for it to launch over x11. I think its something like that??
For example:
GDK_BACKEND=x11 welcome (whatever the app is called)
How do we write environment variables. Do we write into /etc/environment or through a script in our config
we add them to either of these files: /etc/profile, ~/.profile, /etc/xprofile and ~/.xprofile
I don’t know if it is best to add them to the user or for system?
Hmmm. I don’t know?? @joekamprad? Thoughts?
How can we make a test of this? Would like to do test as close to the final netinstall as possible.
Do a base endeavour os install. Pick only base-utlis then run your install script your developing.
But that does not enable LightDM service
It must otherwise nothing would work. None of the other scripts enable lightdm too. Thats done automatically i think
My laptop’s messed up, so after class is finished imma re-install and get working! ( I might use it to test everything out?) @morten-b how’s the install script going?
the package script is not still done @joekamprad sorry! There’s two more thing I know of i need to add! Probably should I checked before I merged it 
. Sorry!
The two things are ttf-nerd-font-symbols and xdg-desktop-portal-wlr
Nowhere currently. Doing my exam all week, so don’t know when I’ll find the time, but I’ll see.
1 Like
Same (or at least I should be!) I’ll try as though I’m copying the files.
Thank You for you help!
feel free to add or remove packages, it is meant as a template used by calamares, read more about YAML format here:
https://docs.fileformat.com/programming/yaml/
Please check for double entries from base install part, and may packages in base not needed o a wayland system (xorg stuff).
The netinstall.yaml file is what shows up on package selection slide inside calamares installer:
I do test this currently in a wm… and yes take the time we are also still working on a convenient way to implement this in a generic way but I start using your config now for testings, the plan is to simply insert the git URL before starting the installer and it will then use the netinstall.yaml and a script from the git repo called setup.sh to inject the setup for the WM/DE after installation is completed from the chrooted_cleaner_script.sh what is running after calamares is read with the system install.
The format of the setup.sh must be followed to work inside chroot and get the users name and chroot path:
#bin/sh
git clone https://github.com/endeavouros-team/i3-EndeavourOS.git
pushd i3-EndeavourOS >/dev/null
cp -R .config /home/$NEW_USER/
cp -R .config ~/
chmod -R +x ~/.config/i3/scripts /home/$NEW_USER/.config/i3/scripts
cp .Xresources ~/
cp .Xresources /home/$NEW_USER/
cp .gtkrc-2.0 ~/
cp .gtkrc-2.0 /home/$NEW_USER/
chown -R $NEW_USER:users /home/$NEW_USER/.config /home/$NEW_USER/.Xresources
popd >/dev/null
rm -rf i3-EndeavourOS
it’s so nice to see it! You made my day thank you!
I’ll study that, double entries there’s a lot those I shall get rid of those. I noticed pulseaudio is in both i3 and base_utlis
How would we exclude stuff in the yaml file.?? Cause we don’t need all of the x-org like you said.