NHey folks, need some help getting this accomplished. I found some relevant documentation to take care of this: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/customizing_anaconda/index#customizing-graphical-elements_branding-and-chroming-the-graphical-user-interface
Nspecifically I need PNGs.
N@Skynet we may need to add some features to Build-Container-Installer to accomplish this.
N@Kyle Gospo @j0rge for visibility.
K@Noel if you send me the files currently in use I can make ublue ones quickly
NI would have to play around with it, I'm not entirely sure. Not super well documented.
Nmain files exist in
/usr/share/anaconda/pixmapsNthe most prominent display of a logo for the silverblue installer I would assume is the
sidebar-logo.pngNI can create an issue in ublue-os/main if that's appropriate. Or I can create issues for both Bazzite and Bluefin.
Kblessed
Make-Fedora-Better.svg21.19KB
Nyeah, double checked the kinoite installer and the most prevalent place it is displayed is in the sidebar
Nwe likely will want to change the color palette to fit Bluefin and Bazzite's themes.
Kpixmaps.7z400.06KB
NCool. If folks want to work on a solution for this, I'm going to take a step back today. I didn't sleep well last night.
SYou should create a
https://weldr.io/lorax/lorax.html#branding
-logos package and then you can either put it higher in the results or an option can be added for custom branding that will add the --skip-branding option and add the specified package to the include list using -ihttps://weldr.io/lorax/lorax.html#branding
NLet's move this discussion to one of the 2 issues I created:
https://github.com/ublue-os/bazzite/issues/1104
https://github.com/ublue-os/bluefin/issues/1284
https://github.com/ublue-os/bazzite/issues/1104
https://github.com/ublue-os/bluefin/issues/1284
SWhich one do you want the discussion in? You went from one to place to discuss it to at least 2 (not counting here)
Nlet's discuss in Bazzite.
NI have them linked to each other, but yeah, probably needed to state that.
KPackaging is for sure the right way, but I don't want to do that
KRight now on our local images we just replaced the existing files
KThat would probably be the best way to accomplish this until we move to the web UI
KDo it right then, you know?
KJust make it a step at the very end of the iso build or something, replace those files and be done with it
EGotta keep the hotdog
