Not at all, there's not even apple silicon ostree images
Not at all, there's not even apple silicon ostree images
GIt's a different bootloader right?
AI made one and was actually able to boot but my Macbook was really slow
ALike 1 second on the clock would take minutes to pass
GAnd kernel + other packages
AThose images still use grub but they chainload from m1n1
AGAh
GSo still a lot of work to be done
AYeah, it's difficult to debug because I have no idea what I'm doing lmaoo
Am1n1 chainloads to uboot and that chainloads to grub
GWould be nice if Marcan or someone on the asahi project helped out with it
AAnd I tried converting a regular fedora Asahi Remix installation to ostree
ABecause there's no installer for this
AAnaconda can't really I guess and Fedora Asahi people use calamares
GBut I understand it's not a priority at all atm
AThey also use KIWI to compose the OS which i have no clue about lol
AIt's the tool used by opensuse
GWhar
GThey use such weird tooling lol
GLike why calemares?
AI think they just like it better
GAh, yeah I'd prefer KDE first time setup + new anaconda webUI
EThat would be sweet. Don't mind looking into that this weekend but not sure I'd be able to figure it out
EOh wait. It's Saturday 
AI built
mkociso to abstract away lorax so currently we can do like this: mkociso --image ghcr.io/ublue-os/bazzite:38 and it will create an ISOAI think the goal is to add something like:
these two templates are what we need to override to hijack the boot menu
these two templates are what we need to override to hijack the boot menu
Aor maybe it should be like:
EEither would be perfect and accomplish what we need to do
EI personally like the second approach
G@tulili hi, I can't respond on github atm but the bling module only pulls in the items specified, sure it's copied into the image, but it's in /tmp, so all of the rpms are removed from the image. Only the ones that are installed are kept inside the image (specified in bling module) bling module also isn't needed in the recipe.yml
GThis also isn't too streamlined, but technically one could define their own repo and add it in the container file, and write an installer script in modules. Would work just fine
TOh hi!
TNo, no, it wasn't exactly that that I was trying to convey, I just thought that maybe by separating where the modules are declared from the repos themselves might be a good idea
TLike, before all files that were cloned onto the images based off of StartingPoint were declared in their own repos, and that made updating things like the ublue-nix-install script a lot worse, since it wasn't necessarily centralized onto one repo (in this case, bling!)
TI just thought that maybe my moving the "modules" folder in the Startingpoint template to other repo, like bling, we could have a better way to keep everyone up-to-date with their module implementations, without requiring them to sync their repos with github's fork thing (which can be very annoying at times when merge conflicts happen)
THaving this pattern someone could just clone their own if they want, too
GSo adding the bling module from the containerfile?
GThe module being contained in the repo?
THmmmm how can I explain it
Tinstead of having this folder at the individual repo level, we could just clone it in the Containerfile from ublue-os/bling:latest
Tlike we can already do with other files in the "files" folder in that image
Tso all standard modules used in startingpoint are defined there and cloned by everyone
Tsomething like this!
Thaving that, someone could just extend the pattern like this
GI like the idea of fetching modules, but we need to figure out how we do documentation for them
GSince currently documentation is in-repo
Toh.....
Tyeah that is an issue
GIt also makes it harder to modify stock modules. I like the idea for the
bling module, as it relies on the bling repo already, but the other modules don't rely on external reposG@hermmm probably has some ideas on this. Moving the docs into the website would probably be the best course of action if we were to fetch modules from a separate repo. Though I dunno if that repo should be bling itself
