KThere's no existing build for that, but one could be made for the desktop build without too much effort
MOh thanks
MI want to use bazzite for gaming but i want to use hyprland
Kif you have anotherh hyprland image
Kyou can just use bazzite-arch in it
Kin distrobox
Xyeah
Xoh it looked like your review would have an impact too
Xbut apparently not
GIt would be a bit of work
GHyprland doesn't use XDG autostart and doesn't have the same feature set as an actual desktop
GI've made a Hyprland spin before, not hard, just need to enable the copr
Kdeck version certainly
Kdesktop version not so much
Ksince it's just steam in a distrobox
GAh
GYou'd need to figure out yafti
Kfor a proper hyprland bazzite you'd need to port system76's scheduler over as well
Kno idea if hyprland has a plugin system
GThey do
Kbut for personal use, honestly just add distrobox and install bazzite-arch
GIt uses lua
Kmuch easier than your own spin
GYeah I'd just use starting point and extend uBlue main
GThen just install bazzite-arch
B@KyleGospo i've tried to use your trick of using the
COPY command based on $image_name to copy certain files for specific image. Only problem is that I have more images than folders to copy. So at some point builds will fail as they cannot copy a non existent folder. Do you maybe have a good solution for that? My thoughts where to maybe copy them first to /tmp and then copy them via the RUN if grep image_name is "silverblue" then cp /tmp/siverblue / because /tmp is cleand up any way. Would something like that make sense?KCan you send me your container file so I can give you the best possible recommendation?
BKThank you, take a look at this as soon as I can
BThe pull request that is open there will add everything that would go in a specific silverblue image for example. and would now also polluting other images if that goes in. To give an extra idea of what is going on
Bthanks for taking a look when you have time, appreciate it
MI finished configuring my custom image
MAnd how to create ublue image?
KAre you going to have anything big in those image specific folders?
KOr is it mostly just bash scripts and configuration stuff?
Bno just configs, for specific images, maybe a service file if needed, backgrounds maybe if location matters. for this is an example of stuff what should go in silverblue specific image https://github.com/ublue-os/framework/pull/10/files
BBut those doesn't make sense in any other image like kinoite or any other non gnome image
KI would go with the solution we landed on prior to the one we ultimately went with
KWhich is to say, have everything in a single folder and copy it into tmp, and then do your image specific checks in a run command instead as a bash if
KThat way you have the option to just do nothing
KSince you're not copying anything of substantial size it's okay to have it all in one layer and shared by every framework image
Kalso reduces your overall layer count since you only have a single copy command
BSo copy everything to /tmp first and copy via bash cp to the location from /tmp?
KWouldn't even need to cp if it's just sh files
KJust if image == Silverblue then; /tmp/Silverblue/my script.sh
KEssentially
Byeah, but some files need to go back into /usr/lib/systemd for example
BI tried this
COPY system_files/desktop/${BASE_IMAGE_NAME} / first as that was a perfect solution. until you build images that you don't have a folder for, then everything bailes outBThanks for your input @KyleGospo
Bi see now in thje commit history you did the same before, first /tmp and then rsync it back
