BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2026//talk//SY7VNU
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-cz-2026-SY7VNU@pretalx.devconf.info
DTSTART;TZID=CET:20260619T144500
DTEND;TZID=CET:20260619T152000
DESCRIPTION:Bootc (bootable containers) enables building bootable host syst
 ems with Containerfiles or any other container build tooling. Bootc presen
 ts a UX challenge: because bootc systems are immutable\, software packages
  must be installed at build-time\, not runtime. To install an additional p
 ackage\, an end user needs to edit their system's Containerfile\, rebuild 
 the image\, `bootc switch` to the new image\, and reboot. This process is 
 more complicated than the traditional `dnf install` UX\, doubly so if the 
 user is directly booting a distribution base image (think Bazzite) and the
 y don't even have a Containerfile to edit!\n\nWhat's needed for `dnf insta
 ll` (or something like it) to Just Work on bootc systems? Is it possible t
 o reconcile imperative package management and declarative container workfl
 ows? And how can we make it fast and reproducible? In this talk\, we'll di
 scuss recent work on `dnf rebuild`\, a new DNF5 plugin that will bring sat
 isfying answers!
DTSTAMP:20260430T125242Z
LOCATION:E112 (capacity 156)
SUMMARY:Local package layering on bootc systems with DNF5 - Evan Goode
URL:https://pretalx.devconf.info/devconf-cz-2026/talk/SY7VNU/
END:VEVENT
END:VCALENDAR