Maybe we should file an issue to ask why glib and xdg-open are in the release tarball
Maybe we should file an issue to ask why glib and xdg-open are in the release tarball
AThat doesn’t seem right at all
EThat would be great
EI'll look around first then file just to be sure. I extracted the last RPM published (one of the 0.4.0 alphas) and they weren't there. Seems off
ATry extracting the tarball manually
AMaybe it’s just tarball being messed up
EI have - they're in the tarball :/
ASounds like a bug
AGitHub
Codespaces but open-source, client-only and unopinionated: Works with any IDE and lets you use any cloud, kubernetes or just localhost docker. - loft-sh/devpod
EI'll open a PR that adds them as excludes
AGreat work 
EI appreciate the help with this. Thank you so much. I wouldn't have thought to do that otherwise
EPR opened
AGlad to help 
Kgreat work you guys, this is excellent
EThank you! PR was just merged too
J
Jyou made the prerelease notes!
J
Jhuh, check this out
LThis might be what I need! 
Jyeah I think @EyeCantCU would wanna see it too
APutting the flatpak installation inside the image means that those applications cannot be removed nor updated
LThat's OK, it's a purpose built image.
I'd use a general image otherwise
I'd use a general image otherwise
EThat's awesome!
EI'll definitely have to take a look at this. Might be the solution we need. Lots of good stuff going down today
LAyy! It worked. Got pre-installed Flatpak applications without post-installation downloading
JDo they just update on first boot?
JAnd did it pull in the runtime?
JAlso I'm sure someone would be interested in centos stream builds 
LI think they’ll update when the image updates, will take an explore!
EWill try this out here in a bit in Bazzite :unstable
JThat's probably more reliable than the first boot systemd service but the tradeoff is size of the iso
EI have an idea though. Create a new tag. Call it release, include the Flatpaks in this tag, use the tag as the default in the installer, then post install you get rebased to latest without the Flatpaks built into the image. They should still be a part of the system
ETag would only get refreshed when release please triggers ISO generation
EI think it's possible at least
EDoesn't work around fighting GHCR for space though
EBut does work around large updates
ANo they won’t be part of the system unless they were reinstalled into a proper location
EBack at square one then unfortunately
AI think maybe I can wire up the Lorax templates to mkociso after tomorrow
JThere's that flatpak issue upstream we got cc'ed on too
EIs remove=image an option?
EOn Bazzite we remove the media writer, cheese, and eog
ENvm. Confirmed for myself lol
Eflatpak remove --installation=image - PERFECT
JI still want a net install with the new UI, maybe someday lol
EWill have to explore that at some point
B@EyeCantCU do you know how many flatpaks does kinoite have and do they get installed when you rebase from silverblue to kinoite
Bbecuase as far as i understand silverblue installs flatpaks during installer
