rpm-ostree is still there to do layering, etc
rpm-ostree is still there to do layering, etc
Bits ment to be a agnostic way to deploy ostree native containers for any distro not just fedora based
Byes
Gnice
Gyeah would be cool to integrate bootc when it's complete
Jyeah and we have no choice
Jthat's how you'll rebase and stuff
Goh so bootc is going to replace the current implementation eventually?
Jyeah
Gnice
Jyou'll be able to podman from any live CD and install too
Gso we don't need to integrate it early then
Jand install other stuff
Jwe'll add it to the image but I suspect fedora will add it first
Jand then the rebase will be
Jbootc rebase ghcr.io/ublue-os/bluefinand that's what the final command will look like
Gdo we have to import the signing keys, etc?
Jthey're looking at the key thing this week
Goh nice
Wwait, it won't just be Fedora then? So like, in theory, down the line we could have something like a Debian base (I guess Endless OS?) Not that it matters all that much, but most of my life I've been in apt land, feels a bit weird leaving it (even if I can just distrobox into my happy place)
Wand if I understood that right, "podman from any boot CD", I'll be able to skip the "have to get a base image then rebase" and just... install my image?
WThe future sounds rad.
Jeven with bootc we need to get offline ISOs sorted out
Glorax looks like the only solution
Gbut idk how to use it
Jyep, we're all stuck in the same boat
Jflock is next week maybe I'll tweet at them to see if someone can help
Git would be so nice if we just made a wrapper for osbuild or lorax where all you gave it was the OCI image
Jyeah
Jjust an action, then anyone can use it
Swhy are other spins (e.g. bluefin) not using the recipe.yml file?
Xthey were created before startingpoint, and some that were not were helped start by jorge who apparently is more comfortable or smn with his own model
Sah ok
Bbecause most spins are older, its also true that basically recipe.yml file is an abstraction on top of the model used by these other spins, for example my images doesnt use recipe.yml as well becuase im more comfortable with lower level concept of editing raw Containerfile
Band its completly ok that images internally made by ublue team use whatever model, point of startingpoint and recipe.yml is to make it easy for everyone to create their own image
Jyeah, believe me, if I could blink and jettison the json file for a proper yaml one I would. 
Jdrops bomb and then leaves for an errand
Salso how would I be going to integrate hyprland to my image?
Slike it use COPR repos https://copr.fedorainfracloud.org/coprs/solopasha/hyprland/
Slike you would just need to run
sudo dnf copr enable solopasha/hyprlandbut when?
Bsilverblue doesnt use dnf
Byou would have to copy the actual repo file into yum.repo.d before rpm-ostree package installation happens
Sah but do i just add RUN wget https://copr.fedorainfracloud.org/coprs/kylegospo/bazzite/repo/fedora-$(rpm -E %fedora)/kylegospo-bazzite-fedora-$(rpm -E %fedora).repo -O /etc/yum.repos.d/_copr_kylegospo-bazzite.repo && \ as an example to dockerfile
Si use the recipe.yml btw
Bthe && \ implies you would run other commands within that RUN step but yes
Bbut since you use recipe.yml under rpm object you ahve a repos array you can add link to
Sso just solopasha/hyprland?
Bno a full link to repo file
