Best practices for exporting from distrobox?
I built a package from scratch in a distrobox, and got to the point of exporting it. At that point, it clicked that the exported app is still run in the container. With that realization, I couldn't decide whether I should create containers for individual packages that I'm exporting, or if I should just keep one per OS, or something in between. Are there general best practices about how to divy up the containers for exporting?
Also, this particular package requires custom rules to be installed in udev. It doesn't seem like the container has the ability to do that, so would this package be better suited to using
rpm-ostree instead, or is there a way I can allow the container to write those rules?10 Replies
Installing and Managing Applications - Bazzite Documentation
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices.
Distrobox
Use any linux distribution inside your terminal.
It'd also be a good idea to say what you are trying to run through the distrobox, since there might be application specific methods that may not require a distrobox
I read through both of those, which is how I got to the point of exporting the app that I compiled. I'm curious about best practices when it comes to exporting multiple apps. Should I make a new container for each app, or should I install however many apps onto one container to export?
Usually there shouldn't be dependency issues
one container for each app makes debugging much easier though
That's what I was leaning towards for organization's sake if nothing else. I'm not super familiar with containers though, so I was worried about spinning up a bunch of containers for no reason and possibly getting performance impacts.
space isn't a too much of a problem because btrfs and duperemove
I've been poking away at https://github.com/jtgans/g13gui so I can use my G13 keypad for games. Switched over from Windows a couple days ago and everything except my keypad has been working wonderfully.
GitHub
GitHub - jtgans/g13gui: A user-space driver and GUI configurator fo...
A user-space driver and GUI configurator for the Logitech G13 - jtgans/g13gui
in that case see if you can use logitech's onboard memory manager to save your profile into the g13 on windows
if not i guess you can try and layer it
Layering worked. And I think it'll work fine with just a manually installed rules file through the export. I might play with that route more tomorrow and see if I can get back to an unlayered build.
Well, that all worked after some modifications to the build and project to make it work on KDE Fedora, so I'll also have to put up a couple PRs tomorrow too.