This might not be the best location for this, but I am not sure where else to put this.Admins can move if needed.
I quite enjoy Archcraft’s prebuilt configs for various window Managers, however I know archcraft is quite meh in other regards, So I decided after experimenting with getting EndeavourOS to work with I3 and KDE Plasma on a VM an idea came to me. What if I install Archcraft for the Tiling WIndow-Manager setup, then add repos and required programs of EndeavourOS.
So I tried it…after a lot of struggling with Corrupt packages due to pgp keys and what not…I finally got it to accept the repos of EndeavourOS and install the base EOS apps and software…after of course some mroe issues with icon symlinks
The next course of action I started to do was try and install EndeavourOS’s packages for KDE Plasma. Once again issues with same files, icons were easy…this time its a config file for sddm. So I made a backup of it and removed it. So it could install packages without errors.
After Rebooting and selecting Plasma X11 (Because VM doesn’t Like Wayland) and I was surprised to see that it was working as intended. EndeavourOS wallpaper, and welcome launcher works…but doesn’t autostart. I also noticed a few missing KDE aplications like the drop down terminal, kde connect…and a few others.
Though overall I’m quite happy with how it turned out. Finally I was able to blend/merge 2 Distros together to make what works for me
I have to say A BIIIIG THANK YOU TO EVERYONE ON THIS FORUM. THEY ALL HAVE BEEN VERY FRIENDLY AND HELPFUL <3
End goal was fun and curiosity. I just posted here so other may know that it works with very little changes or removal of stuff. Just deleting of Qogir Icons, and backing up and removing a file.
To be fair I just posted this in case someone else had a similar idea or gets stuck. I am doing this for fun and learning purposes. That and I enjoy EndeavourOS so far a lot, I just really like archcrafts configs but don’t really know ALL the pre-reqs and how to config properly so I did what I did
I plan to document it more as I actually use it. I mainly was curious because Archcraft has a lot of pre-built configs and even more for the paid prime iso which when melded together like I have…should mean a nice and interesting configs with the robustness of EndeavourOS.
I’m not very experienced with configuring window-managers and such…and I’m only basic Arch user XD…I’m much more use to Debian from little experiments with my Raspberry Pi, and old bare-metal headless mx-linux for few game servers. So I’m just experimenting and learning
I am currently experimenting with this, have one setup on the Raspberry Pi OS and another with Retropie (saving EOS for last, just have a feeling I will stop when I experimenting after I try it
Yeah I love and hate my raspberry pi 4B. While its a great asset for some things…it’s lacking in others but for its price I can’t really complain I guess. For my pi I’ve gotten various Distros working, got it to send data in/out through power port, currently Its my mobile portfolio for server and web stuff to show off.
As for this I probably thread…I probably will continue to post info on it, some screenshots etc. Ideally I will try and make it so I can share these custom configs for a simple and easy install for anyone else wanting similar themes/configs. Me being a pleb when it comes to linux and various customization & ricing of linux Im sure it wil be a lot of fun and learning.
Eventually I also want to learn Nix, Home-manager, and NixOS too…find a way to use them inside EndeavourOS would be useful I think…especially nix package manager, and home-manager…but those are mind bogglingly difficult for me because, mainly its declarative…which leads to the saying…“There is more than 1 way to skinn a cat”…
Well you see that would be the obvious choice…however when I attempted to do that it broke and was unusable. Possibly because I was missing things and pre-reqs that the dot files are referencing. I am a newb when it comes to RICING and what not… So I just tried doing it this way to see if it would work…seemingly enough it worked well. SOOOOOOOO…I plan to use it as a base-line as to figure out why just copying . files didn’t work for me the first time around.
I’m at most things when it comes to ricing…and configuring…slow learner when it comes to it @_@ that and there are so many dot files spread out through many directories I’m sure I missed some too…
I would look at what packages each are using, can’t remember the command rn but the arch wiki can help here, I think its under pacman but you can get it to save what is installed to a file, you can then use this to install these packages on eos and then I would think it should work for yo. Lengthy but fun in way
Yeah, pacman -Q is the command to list all installed packages. Isssue with that is the list is quite long, and I have no idea for specifics. Either way I go about it…it’s going to be a lengthy process of figuring out and breaking down the info.
As I did try just using EndeavourOS fresh install, added archcraft repo, and used archcraft’s wiki to install a pre-configured window manager, but had issues still of missing dependencies. Trying to install specific archcraft stuff also failed to be found even if having archcraft mirrors integrated into the list of repos.
Overall the end goal is to be-able to use just . files and automated install script on EndeavourOS.
The nice thing about VM’s though is I can have both methods side by side, and snapshot as I make changes or before I do…So i can further figure out what is needed, whats not…whats missing etc.
WOW I’m surprised someone would say my method is easier…but I do have to agree. I love archcraft’s pre-configs…they are beautiful work well, and allow for some nice variety and experimentation… However Archcraft is a mess to de-config per say…porting their configs over is a mess to figure out…though to be fair I feel is done intentionally because they want people to support their distro…their losely put since its one guy primarily.
EndeavourOS has such a well documentated, well supported, friendly active community…not to mention tools to easily re-add base eos specific tools, and packages, tools to easily re-add DE/WM, So I found doing it my way worked really well versus the other method of just moving over . files and configs to an EndeavourOS install.
While archcraft has limited community, less active, not as well documented, and no QoL tooling other than basic pre-configs that only work if your actually using archcraft…as just adding the repo and installing misses a lot of things that should be marked as isntall with…
