summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrey Utkin <andrey_utkin@gentoo.org>2019-11-25 19:23:29 +0000
committerAndrey Utkin <andrey_utkin@gentoo.org>2019-12-03 13:32:16 +0000
commitb8e400e247f95542ea116b4c5c1d4675c12dfc5e (patch)
tree3a98113d5021c36861fd6a3188ac269f9c0e4690 /sys-boot/raspberrypi-firmware
parentsys-boot/raspberrypi-firmware: don't install device tree blobs (diff)
downloadgentoo-b8e400e247f95542ea116b4c5c1d4675c12dfc5e.tar.gz
gentoo-b8e400e247f95542ea116b4c5c1d4675c12dfc5e.tar.bz2
gentoo-b8e400e247f95542ea116b4c5c1d4675c12dfc5e.zip
sys-kernel/raspberrypi-image: install device tree blobs
Upstream git repo provides binaries of two natures in a single repository: * boot firmware files; * prebuilt kernel files. boot/*.dtb, boot/overlays/ belong to kernel, not boot firmware. But for historical reasons, these files were installed by sys-boot/raspberrypi-firmware package rather than sys-kernel/raspberrypi-image, which would be more correct. The problem with this is that users of kernels different than sys-kernel/raspberrypi-image need to install different files into these locations. This means such people have to avoid using sys-boot/raspberrypi-firmware package completely. A blocker dependency on old sys-boot/raspberrypi-firmware versions is added to protect from a situation when just raspberrypi-image is being upgraded, and a package manager ends up with a file collision during installation phase. Package-Manager: Portage-2.3.66, Repoman-2.3.16 Signed-off-by: Andrey Utkin <andrey_utkin@gentoo.org>
Diffstat (limited to 'sys-boot/raspberrypi-firmware')
0 files changed, 0 insertions, 0 deletions