BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.nix.vegas//2026//talk//SRRBTB
BEGIN:VTIMEZONE
TZID:PST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T100000Z
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T110000Z
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-2026-SRRBTB@cfp.nix.vegas
DTSTART;TZID=PST:20260807T140000
DTEND;TZID=PST:20260807T143000
DESCRIPTION:Nix’s guarantee of reproducibility hinges on a simple mechani
 sm: absolute\, immutable store paths (i.e. /nix/store). While this rigidit
 y guarantees that binaries always find their exact dependencies\, it intro
 duces a massive constraint: it binds the entire ecosystem to a single\, gl
 obal directory. If you want to run a Nix binary on a target system where y
 ou don't have root access to create /nix\, or where you cannot run an unpr
 ivileged user namespace\, you are forced to rebuild the world To achieve t
 rue portability and friction-free deployment across arbitrary infrastructu
 re\, Nix binaries must become fully relocatable. What does that mean ? Why
  is it hard? Who cares (psst me!)? We will discuss what a fully relocatabl
 e Nix ecosystem could look like \, and how solving this constraint could a
 llow Nix to be run more easily on more restrictive environments..
DTSTAMP:20260725T043620Z
LOCATION:Nix Vegas Main Stage
SUMMARY:Relocatable Nix Binaries - Farid Zakaria
URL:https://cfp.nix.vegas/2026/talk/SRRBTB/
END:VEVENT
END:VCALENDAR