From: "Andrey Utkin" <andrey_utkin@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-boot/raspberrypi-firmware/
Date: Tue, 3 Dec 2019 13:34:25 +0000 (UTC) [thread overview]
Message-ID: <1575379932.1618c312961d281be9e971e8040d41e6423b2554.andrey_utkin@gentoo> (raw)
commit: 1618c312961d281be9e971e8040d41e6423b2554
Author: Andrey Utkin <andrey_utkin <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 25 18:54:39 2019 +0000
Commit: Andrey Utkin <andrey_utkin <AT> gentoo <DOT> org>
CommitDate: Tue Dec 3 13:32:12 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1618c312
sys-boot/raspberrypi-firmware: don't 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-kernel/raspberrypi-image versions is
added to protect from a situation when just raspberrypi-firmware is
being upgraded, and the machine ends up not having device tree files.
Upgrading to a new version may cause a disruption if the user doesn't
use sys-kernel/raspberrypi-image but still relies on device tree files
installed by raspberrypi-firmware package. This will be dealt with by a
news item. A special USE flag for smooth transition of such users is
considered an overkill, on presumption that this package is not
massively popular.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Andrey Utkin <andrey_utkin <AT> gentoo.org>
sys-boot/raspberrypi-firmware/raspberrypi-firmware-9999.ebuild | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/sys-boot/raspberrypi-firmware/raspberrypi-firmware-9999.ebuild b/sys-boot/raspberrypi-firmware/raspberrypi-firmware-9999.ebuild
index 4b06dfa4993..e1ebbe9b7e4 100644
--- a/sys-boot/raspberrypi-firmware/raspberrypi-firmware-9999.ebuild
+++ b/sys-boot/raspberrypi-firmware/raspberrypi-firmware-9999.ebuild
@@ -10,6 +10,12 @@ HOMEPAGE="https://github.com/raspberrypi/firmware"
LICENSE="GPL-2 raspberrypi-videocore-bin"
SLOT="0"
+# Temporary safety measure to prevent ending up with a pair of
+# sys-kernel/raspberrypi-image and sys-boot/raspberrypi-firmware
+# none of which installed device tree files.
+# Remove when the mentioned version and all older ones are deleted.
+RDEPEND="!<=sys-kernel/raspberrypi-image-4.19.57_p20190709"
+
if [[ "${PV}" == 9999 ]]; then
inherit git-r3
EGIT_REPO_URI="https://github.com/raspberrypi/firmware"
@@ -45,8 +51,6 @@ src_install() {
insinto /boot
cd boot || die
doins bootcode.bin fixup*.dat start*elf
- doins *.dtb
- doins -r overlays
newins "${FILESDIR}"/${PN}-0_p20130711-config.txt config.txt
newins "${FILESDIR}"/${PN}-0_p20130711-cmdline.txt cmdline.txt
newenvd "${FILESDIR}"/${PN}-0_p20130711-envd 90${PN}
next reply other threads:[~2019-12-03 13:34 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 13:34 Andrey Utkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 14:55 [gentoo-commits] repo/gentoo:master commit in: sys-boot/raspberrypi-firmware/ Viorel Munteanu
2024-10-24 11:42 Viorel Munteanu
2024-09-07 12:04 Viorel Munteanu
2024-09-06 8:58 Viorel Munteanu
2024-09-06 8:58 Viorel Munteanu
2024-04-20 3:20 Sam James
2023-03-24 13:45 Arthur Zamarin
2023-03-10 6:02 Dennis Lamm
2023-03-04 6:36 Arthur Zamarin
2023-03-04 6:03 Arthur Zamarin
2023-02-02 20:05 Dennis Lamm
2023-02-02 20:05 Dennis Lamm
2022-12-22 11:10 Dennis Lamm
2022-12-22 11:10 Dennis Lamm
2022-10-24 17:16 Dennis Lamm
2022-10-24 17:16 Dennis Lamm
2022-10-24 17:16 Dennis Lamm
2022-04-17 16:44 Sam James
2022-04-09 19:58 Arthur Zamarin
2022-04-09 19:57 Arthur Zamarin
2022-04-06 6:57 Dennis Lamm
2022-02-20 5:51 Sam James
2021-12-14 20:47 Arthur Zamarin
2021-12-14 2:06 Sam James
2021-12-05 1:28 Sam James
2021-11-21 8:21 Sam James
2021-06-21 22:36 Sam James
2021-03-06 7:26 Sam James
2021-03-05 20:34 Sam James
2021-01-27 7:31 Sam James
2021-01-25 14:06 Sam James
2021-01-25 14:04 Sam James
2020-12-20 6:29 Sam James
2020-12-11 22:12 Sam James
2020-12-11 21:35 Dennis Lamm
2020-12-10 17:43 Sam James
2020-11-23 5:01 Sam James
2020-11-23 4:54 Sam James
2020-07-28 0:10 Sam James
2019-12-30 22:33 Andrey Utkin
2019-12-03 13:34 Andrey Utkin
2019-07-15 20:31 Andrey Utkin
2019-07-05 21:38 Andrey Utkin
2019-03-25 23:07 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2019-03-24 19:18 Andrey Utkin
2017-10-15 9:21 Michael Palimaka
2016-03-15 13:49 Michael Weber
2016-02-19 21:55 Michael Weber
2016-02-19 21:55 Michael Weber
2015-11-29 20:22 Alfredo Tupone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1575379932.1618c312961d281be9e971e8040d41e6423b2554.andrey_utkin@gentoo \
--to=andrey_utkin@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox