Open KyleGospo opened 7 months ago
Suggestions:
Utilities that would likely be helpful:
Things that would be cool, but totally not necessary/probably out of scope:
That would seem interesting! Getting JetBrains IDEs installed through a copr is a bit of a hassle and there doesn't seem to be a way to make JetBrains Toolbox run on a specific Distrobox container (obviously excluding the AUR package), because of how it installs, it can only install on the host, where there won't be any (other than probably Python) SDKs installed.
That would seem interesting! Getting JetBrains IDEs installed through a copr is a bit of a hassle and there doesn't seem to be a way to make JetBrains Toolbox run on a specific Distrobox container (obviously excluding the AUR package), because of how it installs, it can only install on the host, where there won't be any (other than probably Python) SDKs installed.
The challenge here is, you can't throw all of them into one distrobox image (nor do people need all of them... usually) as the size is too big for GHCR unless you do it after the fact
One solution would be using distrobox assemble for each JetBrains IDE, keeping the environment completely separate from one another, installing everything while setting the image up on the host
Another alternative is one distrobox instance that provides everything needed by each IDE with just scripts that install whatever IDE you need
Jetbrains has it's own "toolbox" that people have been using and so far the feedback has been positive: https://universal-blue.org/images/bluefin/developer-experience/#jetbrains
Jetbrains has it's own "toolbox" that people have been using and so far the feedback has been positive: https://universal-blue.org/images/bluefin/developer-experience/#jetbrains
Toolbox works great for that but these are all installed as AppImages that rely on the host to provide individual SDKs. Providing a path isolated from the host that's reusable anywhere could be an awesome way of managing that. Brainstorming ways of doing that
As a reminder, distrobox has a --home flag that lets you specify an alternative home directory for the container user, which, coupled with distrobox-enter -n (containername) -- (executable in absolute location)
, may solve the issue. Distrobox can export any binary a container can see.
Integration with game engine like Unity,Godot,and maybe Unreal Vscode pre-installed will be huge plus and maybe Docker too?
Integration with game engine like Unity,Godot,and maybe Unreal Vscode pre-installed will be huge plus and maybe Docker too?
what advantages does docker have over podman?
not quite sure if those are really "advantages"
more compatible with stuff for example i tried to use devcontainers on bluefin image and it just PITA, meanwhile docker works ootb
I would like a distro that has preinstall the following software:
Software I'd like to see that I haven't seen others post:
I would suggest to have all the necessary stuff that are common for the majority of developers and are commonly used (podman, vscode, configs etc). As for the rest, they can be installed seperately.
I would imagine, for example, i as an android developer, if i wanted android studio ready, maybe i could do ujust android-studio
Integration with game engine like Unity,Godot,and maybe Unreal Vscode pre-installed will be huge plus and maybe Docker too?
what advantages does docker have over podman?
For me it's just a requirement for collaborating with others who all use Docker.
I would definitely appreciate an easy way to get docker up in Bazzite. It works in Bluefin out of the box, but getting docker working properly is a pain on just about every other atomic system that I've used.
IMHO VMware, VirtualBox, and anything that requires kernel modules should be built in. At least the kernel module part - so that when user needs those tool, they can just be installed from a menu/command.
As long as that's done, I think everything else can just be thrown to different yafti menu/sub-categories.
Why not start with only whatever -dx adds to Bluefin? Related: https://github.com/ublue-os/bluefin/issues/1321
Extra
repository.Nodejs
Java gui
There certainly needs to be a scope that needs to be referred to.
There's many suggestions of general development tools, rather than what I thought this was intended to be - a game dev image.
If we add everything from Bluefin DX, then we've just replicated Bluefin.
There certainly needs to be a scope that needs to be referred to.
There's many suggestions of general development tools, rather than what I thought this was intended to be - a game dev image.
If we add everything from Bluefin DX, then we've just replicated Bluefin.
Would that really be the case? Because Bazzite has a lot of things I wanted for Bluefin DX like OpenRazer, Emudeck, OpenTabletDriver, Sunshine, Waydroid, etc. Whereas Bluefin has things I want like Jetbrains toolbox. cockpit, Gnome VRR, VFIO, ollama, etc.
Im thinking about making my own image or configuration and I dont even know which would be the correct base because both seem to have what I want.
I want bluefin-dx but on bazzite. To me that would be the main base for gamedev. I wouldn't include any software that doesn't require configuration in order to fully function. At a minimum: I need devcontainers working out of the box with vs code.
I want java and nodejs
I want java and nodejs
for java and nodejs you can use homebrew
I want java and nodejs
for java and nodejs you can use homebrew
Java isn't on homebrew
I want java and nodejs
for java and nodejs you can use homebrew
Java isn't on homebrew
Similarly to Bluefin-DX, we'd like to ship DX images which come preconfigured with common game development and debugging tools. If you're a developer we'd love to hear what you might find useful in an image like Bazzite.