Other overlays have placed image writing tools (e.g. rpi-imager, balena-etcher, et al) under the package category of 'sys-boot'. This determination is logical as executables are writing a disk image to a new boot device. However, change to 'sys-boot' has not been made in guru packaging tree. Package 'rpi-imager' is still listed under 'dev-util'. A search for 'rpi-imager' in emerge, or other tools, causes problems because of the multiple package categories. Request tree make change to re-categorize package for consistency with other overlays.
The request is perfectly reasonable, but one question: > A search for 'rpi-imager' in emerge, or other tools, causes problems because of the multiple package categories. I don't get what this part means?
----- scottfurry@athens /var/db/repos/FurCaT $ emerge -p rpi-imager These are the packages that would be merged, in order: Calculating dependencies - [ Results for search key : rpi-imager ] * dev-util/rpi-imager [ Masked ] Latest version available: 1.8.5 Latest version installed: [ Not Installed ] Size of files: 21,930 KiB Homepage: https://www.raspberrypi.com/software/ https://github.com/raspberrypi/rpi-imager Description: Raspberry Pi Imaging Utility License: Apache-2.0 * sys-boot/rpi-imager Latest version available: 1.8.5-r1 Latest version installed: 1.8.5-r1 Size of files: 21,930 KiB Homepage: https://github.com/raspberrypi/rpi-imager Description: Raspberry Pi Imaging Utility License: Apache-2.0 [ Applications found : 2 ] !!! The short ebuild name "rpi-imager" is ambiguous. Please specify !!! one of the above fully-qualified ebuild names instead. ... done! Dependency resolution took 5.16 s (backtrack: 0/20). -----
(In reply to Scott Furry from comment #2) Isn't that just because you (or another repo you use) has, for some reason, chosen a different name? While I agree that it should be in sys-boot (probably), there's no strict canonicalisation of names, so the issue is the fact that something chose a different name, rather than the move actually helping here. (If the *same repository* has the same package twice under different names, that's also a bug in its own right.)
(i.e. I don't think there's anything inconsistent about it other than wrt other packages, unless you're saying that package appears twice in ::guru; you're just proposing it be renamed.)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=8f46243037d3be220578b46948c96e08ca5631f3 commit 8f46243037d3be220578b46948c96e08ca5631f3 Author: Takuya Wakazono <pastalian46@gmail.com> AuthorDate: 2024-11-10 03:34:07 +0000 Commit: Takuya Wakazono <pastalian46@gmail.com> CommitDate: 2024-11-10 03:35:51 +0000 profiles: mask dev-util/rpi-imager for removal Bug: https://bugs.gentoo.org/942894 Signed-off-by: Takuya Wakazono <pastalian46@gmail.com> profiles/package.mask | 8 ++++++++ 1 file changed, 8 insertions(+)
