-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Installer #2
Comments
This would be pretty hard to do. Anaconda does everything from boot configs to package setup. We can probably just make a new installer frontend based on the Anaconda API, but the API is still not stable. |
Hmmm, fair point. I think it might be worth it to use Anaconda's API with our own frontend, even if it's unstable. |
Recently, Anaconda has added a Web UI functionality, so we can probably look into how they work with Cockpit and replicate the API for ourselves. |
Honestly, I feel like picking this up, need a new tau project to work on :p I'm still undecided if I want to use anaconda or not as a backend |
Anaconda is incredibly customizable, but you'd have to use python. What I'm thinking we can do is a dual backend system. On tauOS we manually deploy the OSTree to the drive. On Ultramarine we can use distinst |
I see no reason why we couldn't use distinst for this as well, since it takes a squashfs for deployment in which we could stage an OSTree deployment on. |
Sounds good to me |
UPDATE: Please see https://github.com/FyraLabs/readymade |
Anaconda, Fedora's installer, isn't great UX wise. There's an opportunity for us to significantly improve the installation experience (and maybe even the speed too) through our own installer.
The text was updated successfully, but these errors were encountered: