ublue using OCI images seems a bit similar to nixOS in some ways
ublue using OCI images seems a bit similar to nixOS in some ways
Adifferent ways to obtain reproducible builds
AYou could even port Batocera over to ublue if you ever wanted to
ZThe language is fine itself, rather is just the amount of bloat.
Tbloat?
Ni wonder if someone made a nix-based distro that uses nix to build oci images then run that on ostree
Ni have no idea what the practical purpose of that would be
Nso, it's a blessing?
ZAlso the nix filetree shenanigans and a lot of small issues
ZAt a very basic level is fine.
N
Ni do not need to use a flake based config
ZAnother issue is the documentation that is not in a simple single page, cuz now reading this, would have solved a lot of my issues 
Ni like it personally
Nif you aren't me and don't reformat a partition without updating the hardware config you won't have problems
KIt's built-in on every image
KIncluding testing
KGoverlay was the only thing temporarily dropped
Hoh its temporarily dropped, cool
KRight, surface and framework images are dead
KAnd I'm hoping to kill Asus here soon too
KAlready restored on testing
Aif people want fan curves and charge limiting with simpledeckytdp they need asusctl
KYeah, I'm planning to keep that, but just install it a different way
KLikely as a systemd sysext
Abe careful with that it locks the fs
Alol
H@robinustream 
goverlay returning, so if you layered it, make sure you remove it before updating to 40 when it releases
goverlay returning, so if you layered it, make sure you remove it before updating to 40 when it releasesAits a rust bin tho, should be able to drop it in with its rules in /etc/udev or sth
K
KGitHub
Build your own custom Universal Blue Image! Contribute to ublue-os/image-template development by creating an account on GitHub.
Ahow does that work with secure boot
Ais only the kernel affected?
KIf you don't touch the kernel you can continue to use it exactly as it is now
Adoes that upload the whole image?
KYes, you're making your own on GitHub
Aor only the extension layers
KEither fork or FROM
KWhole image either way
Acan you pin some images so they dont expire after 90 days?
KYep, same as us
KSame build process
Acan you not me
Ai guess yes
Apin the 0220 and the other image aru says are good
Afor good measure
Abefore they expire
KOh, pin in GitHub
KI don't believe so, no
