# Our stable releases win over Debian's packages (500), whatever the versions; below 1000, so a
# newer dev build installed from ps3-dev is never downgraded: the next stable release (a higher
# version) takes over from it. Going back to an older version is explicit: apt install pkg=<ver>
Package: *
Pin: release o=PS3, n=ps3, c=main
Pin-Priority: 990

# Licensed content (classicube-data, game data) like the stable suite: it never has dev builds, a
# dev build of the engine (from ps3-dev) takes its data from here
Package: *
Pin: release o=PS3, n=ps3-licensed
Pin-Priority: 990

# Dev builds only when asked for (apt install -t ps3-dev ..., make deploy), like Debian's
# experimental
Package: *
Pin: release o=PS3, n=ps3-dev
Pin-Priority: 1

# Debian's kernels and Mesa are never installed: the PS3 runs ours (Debian's linux-libc-dev,
# linux-base, perf etc. stay installable). A Debian package needing a newer Mesa than ours is
# kept back by apt upgrade, nothing is removed.
Package: linux-image-* linux-headers-* linux-kbuild-* linux-support-* src:mesa
Pin: release o=Debian Ports
Pin-Priority: -1

# The deps component holds Debian packages for offline installs and rollback: only when
# nothing else has them
Package: *
Pin: release o=PS3, n=ps3, c=deps
Pin-Priority: 100
