When is the switch to bootc + dnf5 expected?

General
1

Jorge talked about it, but will this be part of F42 or is this more of an F43-44 thing?

1 Like
2

We switched to bootc and dnf already this cycle.

4 Likes
3

Then why do I need to still use rpm-ostree to overlay stuff?

4

You need to use rpm-ostree for layering, because layering is not (yet) implemented in bootc.

5

Seem a bit premature to switch to bootc then, if it is missing functionality.

1 Like
6

These people, et al., know what they are doing.

image
image411×1499 161 KB

7

I fully appreciate and deeply respect everything the fine team here has done. However, 38 years of IT experience tells me that if the new function does not have all of equivalent major features of the old function, it’s not ready for primetime.

1 Like
8

I think you’re misunderstanding our scope, we’re defaulting to image mode and moving away from local layering entirely.

You’ll need to toggle a config and do all that stuff by hand, that’s not changing so you’ll just continue to use rpm-ostree.

1 Like
9

Just to clarify, if the image does not EXACTLY meet your needs, you have to disable the new hotness and switch back to rpm-ostree?

1 Like
10

Yeah, it’s just how it is today except you have to change a config file. But all of this is day zero stuff, after installation you just leave it.

Are you finding yourself using rpm-ostree often to install RPMs etc?

11

I’m a photographer, not a developer. Many of the tools I use need access to hardware acceleration not provided by flatpak (AMD GPU specifically). Most everything else is fine as I can usually get by with distrobox.

12

Ok so if it’s set up now you won’t need to mess with it. After everything is setup all the stuff still updates normally.

13

Thank you for the clarification.

14

This:

and

  • some features from rpm-ostree are moving to bootc and some are planned to be in dnf (like layering)
  • rpm-ostree will still be present until all features are made equal

Can you list them here… maybe some other way exists to install them.

15

I have a Framework 13 AMD laptop. I use darktable. It needs OpenCL for accelerated processing of images which makes a significant difference in performance. The flatpak version only supports Nvidia OpenCL as AMD is not available in flatpak. Trying to run this config in distrobox is a bit unstable and I end up overlaying the OpenCL stack on bluefin. Ructicl is an option but it requires the latest version of mesa but that cannot be overlayed as it conflicts with the pinned version in the OS.

My preferred terminal is ghostty and it is not available via brew for linux. There is a repo in COPR that allows overlay. Installing via distrobox is out because the terminal points to the inside of the container and not the OS in general. The flatpak is under contruction and there are some upstream hurdles that need to be attended to before it is released. The flatpak is a community effort. I find appimages hit or miss with atomic OS’s although the gearlever flatpak app makes updates much simpler. Boxbuddy supports ghostty as a terminal. It would be nice to include it in the base image with a ujust toggle to swap it in for ptyxis (which is not my cup of tea).

16

Previous discussion. Sounds like there might be hope.

17

You can build a static binary from source on a fedora distrobox. The binary will work on the host.