We will be able to support other distros but right now bootc itself depends on rpm
We will be able to support other distros but right now bootc itself depends on rpm
Bwindows installer is probably the closest thing to best i can think off(and people dont like my opinion) its simple everything but what is actually needed is outside of the installer
Bi cant wait for that to get sorted.
AThe current windows installer is kinda terrible
AUnless you only count the part before it reboots for the first time
Bthats the installer before reboot
Bafter reboot is out of box experiance
AI count that as the installer as the whole thing because it takes like 30 mins and a bunch of questions after reboot
AIn a way I would consider the gnome first boot setup part of the installer as well
Bi dont installer is what installs the OS. just like i dont consider gnome first boot part of installer
Bto me those are seperated from installer
NYeah it's easy enough to understand, partitioning tools are a bit basic but they obv include only what the user needs
Band OOBE from windows is just sad
Nmostly useless yea
Nit has fun animations though lol
Byou realy dont need much for windows drive partitioning, they could have an automatic one but this does the job just as well as its ment to be used by someone who knows what they are doing
AFor example if gnome first boot experience doesn’t run the system is unusable
Ahence at that point to me the OS is half installed
Bwell its still not part of installer it may be part of the experiance but not installer itself
BOS is installed whether you finish OOBE(or gnome first boot) but its not configured
AI mean you could say the system is installed after the rootfs is unpacked by that logic
Bto me they are 2 seperate parts and i treat them as such
Bthey are clearly 2 seperate components
AThey’re two separate components but parts of the same process
Acleaned up mkociso and made it an independent tool, two features I want to add:
boot_menu.ymlsupport- Custom boot params from boot_menu.yml
- Custom Lorax template support
WJust testing the OBS Studio container image again. Sadly I am still see this:
KHi, what command did you use to create the container?
Wdistrobox create --image ghcr.io/ublue-os/obs-studio-portable:latest --name obs-portable --pull and then entered the container.WAnd then ran
/opt/obs-portable/obs-portableWAny objection to a pull-request that creates the required
/opt/obs-portable/config with 0777 and drops effort the symlink a to config directory in home?AWe removed the symlink in place of a volume and a hack to bind mount the volume in the right place
AWhat’s your shell?
WMy default shell is
fish, but that shouldn't be an issue as I'm sure the script that is invoked has a suitable shebangAThe hack relies on a script in
/etc/profile.dAWhich only gets read by bash, it’s very ugly m
WJust checked, the is not
config directory in /opt/obs-portable.WAh.
Kcould do it this way
KKjust need to pre-make /opt/obs-portable/config
Kso it doesn't blow up on not finding it
WI'm running NixOS. There is no
/etc
A/etc inside the container
AOh sorry wrong reply
W
AThere is a typo
AGitHub
Martin was here. Contribute to ublue-os/obs-studio-portable development by creating an account on GitHub.
A2
WThere are two errors in 
/etc/profile.d/99-obs-config-fix.sh, I'll file a pull request ASorry I beat you to it
