Are you going to have anything big in those image specific folders?
Are 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
KIf you need more than that I'm afraid you'd need separate containerfiles
KOr empty folders in git (hack)
KMaybe a simple dotfile in there to get it to be kosher
G@hermmm do you want to make another blogpost before merging everything?
B
Jgot it!
Binteresting it did change my background and other settings, but not my text-scaling
G@j0rge would you mind approving the startingpoint rewrite and the related website PR?
https://github.com/ublue-os/startingpoint/pull/135
https://github.com/ublue-os/startingpoint/pull/135
GitHub
This is an ongoing WIP rewrite for startingpoint to make it more modular. Comments appreciated. Code will be running through shellcheck.
Made this a 1.0 goal since I wouldn't do a "first r...
Made this a 1.0 goal since I wouldn't do a "first r...
GI approved the PR but I don't have any write access to startingpoint or the website, so I can't get it to pass checks
KI approved it, if you link me to the website one I'll do that too
GGitHub
This PR should be merged right after ublue-os/startingpoint#135
GSeems like it's all ready to merge
GJust gotta merge em at the same time
KI can add them both to the merge queue now if you want
KBoth are approved
GYeah, I was gonna ask about another blog post but it seems like the old one has been updated accordingly
GSo yeah I'd just add them to the queue
KDone
GOk, I see a few things off with the docs
GI'll create a PR to fix some of them (it's mostly just small typos + some consistency issues)
WOOOKkk. Sitting down and trying out forge. Lets work through this. Step 0: a brand new install of ucore. First thing:
./forge setup failsWWI can post the full stacktrace if it helps
Gsubmitted PRs for formatting, my work here is done 
G(ready to merge if anyone wants to approve them and add them to the queue)
https://github.com/ublue-os/bling/pull/35
https://github.com/ublue-os/website/pull/446
https://github.com/ublue-os/bling/pull/35
https://github.com/ublue-os/website/pull/446
K@wimpress I just realized we got a free benefit for containerizing your copy of OBS and didn't capitalize on it
KWe should install AMD GPU pro in there
KIt'll work even if the host only has mesa, and then we get AMF
KWithout having to do any of the messy stuff like specifically only using AMD GPU pro on obs and moving the Vulkan file out so other games don't use it
K@j0rge
Xdeploying to https://ublue-images-demo.netlify.app/ is still manual due to ublue org perms, so i had forgotten to manually deploy a previous release too. and using the startingpoint github repo as a template is not allowed either
Xbut anyway, now it should be fixed for the rewrite.
DI have a major question. Why can you install akmods on stock silverblue or kinoite but it will fail to install on any ublue os?
