FIt's annoying to build in a containeruse the containers package manager?
Fwait what?
A
Fwow
Ksudo ln -s /usr/bin/distrobox-host-exec /usr/bin/rpm-ostreenow you can just call rpm-ostree
Kand it'll call it on the host
Kit takes the name it was called as in as an arg
Kand then calls it on the host
Kpassing in any other arguments
K
Khere's the same thing done for /usr/bin/flatpak
Kcalling flatpak on my host, in a fedora distrobox
Fwhats the point of this?
Ksee above
Kalso,
sudo ln -s /usr/bin/distrobox-host-exec /usr/bin/xdg-openbtw you also can use brew to install host cli app
Know when something tries to open a file browser or a web link or whatever
Fwhere
Kit opens on my host
Fohhhhh
Fthat makes sense
Fwhy would you want to do this btw?
Rso that you can stay inside your container but still be able to run stuff on your host
Rlike updates or stuff
Fohh ic
CIs there a way to factory reset Bazzite? Erase all user data but keep OS?
Jthis channel is for ublue-dev, #bazzite-help for support. The current answer is now but we're looking for someone to help implement it: https://github.com/ublue-os/main/issues/95
J
Jwhen did we do this monochrome icon for the website?
Jthat looks SO good
Jpretty sure it wasn't there before
NBecause we fancy
NAnd color changing of an svg is easy
Jwe need this on the forum logo, it's not awesome
ALooks too good
DGitHub
This is tiny, 8.5k and should probably go here and not in bluefin
Fixes: ublue-os/bluefin#1610
Thank you for contributing to the Universal Blue project!
Please read the Contributor's Guide ...
Fixes: ublue-os/bluefin#1610
Thank you for contributing to the Universal Blue project!
Please read the Contributor's Guide ...
Dor just CLI?
EGUI
F@Kyle Gospo I think I found the better way of modifying default settings for GTK flatpaks
We can modify default settings in gschema itself in
Then compile the gschema there with
However, this has to work in run-time (in flatpak-manager script, however it's called).
So placing GTK settings in
Those 2 approaches combined should assure that modified flatpak settings stick, even with flatpak data removal
Only time-window where they don't stick, is in the below conditions together:
- when flatpak app got updated, but script didn't ran again in that time period (flatpak update overwrites everything in
-
We can modify default settings in gschema itself in
/var/lib/flatpak/app/app_id/current/active/files/share/glib-2.0/schemas/name_of_gschema.xmlThen compile the gschema there with
glib-compile-schemasHowever, this has to work in run-time (in flatpak-manager script, however it's called).
So placing GTK settings in
skelThose 2 approaches combined should assure that modified flatpak settings stick, even with flatpak data removal
Only time-window where they don't stick, is in the below conditions together:
- when flatpak app got updated, but script didn't ran again in that time period (flatpak update overwrites everything in
/var/lib/-
skelsounds great!
Fwhat happens when i do
sudo make installmake installed
ZMost likely only available in the container
Fhow confident, im too scared to try it out lol
ZDepends on the make file mostly
Flets say it installs in /usr/local
ZThat would be container side
Foh okay thats all good then
ZEverything is on the container side except /home most of times
Fawesome alright
