From f11264e6122c6ff8d3ee56c7faa565d8e67a6a5c Mon Sep 17 00:00:00 2001
From: Steve Arnold <sarnold@vctlabs.com>
Date: Wed, 10 Apr 2024 11:41:28 -0700
Subject: [PATCH] dev-python/adblockparser: fix pyre2 consumer and update
 readme

Signed-off-by: Steve Arnold <sarnold@vctlabs.com>
---
 README.rst                                    | 23 +++++++++++++++----
 .../adblockparser/adblockparser-0.7.ebuild    |  9 ++------
 2 files changed, 21 insertions(+), 11 deletions(-)

diff --git a/README.rst b/README.rst
index 5be7276..58a0a40 100644
--- a/README.rst
+++ b/README.rst
@@ -61,12 +61,27 @@ Run the following command to sync the repo::
 
   # emaint sync --repo embedded-overlay
 
+Updating md5-cache
+------------------
+
+The directory metadata/md5-cache can contain cache files to speed up portage
+when working with ebuilds from the overlay. This overlay does not include
+these files, so it is recommended to generate these yourself. To do that,
+simply run the following as root::
+
+  egencache --update --repo=embedded-overlay
+
+
 WIP embedded kernel-bin ebuild
 ==============================
 
 This is currently a WIP convenience ebuild for installing a generic kernel
 binary on something small/embedded that can't run the full distro-kernel bin
-package.
+package. There are also some experimental github CI kernel builds here:
+
+https://github.com/sarnold/arm64-mainline-linux/releases
+
+Feel free to request a tagged build for something specific.
 
 In this context, "generic kernel" is built using something like the RCN
 `build scripts`_ (forked) or one of the many upstream `kernel builders`_.
@@ -86,11 +101,11 @@ should look something like this::
   deploy/6.5.8-arm64-r1.Image
   deploy/config-6.5.8-arm64-r1
 
-To use the ebuild on an arm64 host with the above build output, the steps
+To use these ebuilds on an arm64 host with your own build output, the steps
 are essentially:
 
 * drop the artifacts in your local distfiles
-* (re)generate the ``cross-kernel-bin`` Manifest file
+* bump the version as needed and (re)generate the ``cross-kernel-bin`` Manifest file
 * emerge ``cross-kernel-bin`` as you normally would
 * if needed, generate your initramfs (eg, dracut)
 * run ``grub-mkconfig`` --or-- update extlinux.conf
@@ -255,7 +270,7 @@ short ebuild listing::
   │   ├── msgpack
   │   ├── pdfrw
   │   ├── picotui
-  │   ├── py-re2
+  │   ├── pyre2
   │   ├── pymavlink
   │   ├── pystache
   │   ├── python-uinput
diff --git a/dev-python/adblockparser/adblockparser-0.7.ebuild b/dev-python/adblockparser/adblockparser-0.7.ebuild
index 2b97841..2d283a3 100644
--- a/dev-python/adblockparser/adblockparser-0.7.ebuild
+++ b/dev-python/adblockparser/adblockparser-0.7.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=8
 
-PYTHON_COMPAT=( python3_{8..10} )
+PYTHON_COMPAT=( python3_{9..12} )
 DISTUTILS_USE_SETUPTOOLS=bdepend
 inherit distutils-r1
 
@@ -22,15 +22,10 @@ fi
 
 LICENSE="MIT"
 SLOT="0"
-IUSE="test"
 RESTRICT="!test? ( test )"
 
 RDEPEND="${PYTHON_DEPS}
-	dev-python/py-re2[${PYTHON_USEDEP}]
-"
-
-DEPEND="
-	test? ( >=dev-python/pytest-3.0.3[${PYTHON_USEDEP}] )
+	dev-python/pyre2[${PYTHON_USEDEP}]
 "
 
 DOCS=( README.rst CHANGES.rst )