root@mowa219-gjp4-8570p-freebsd:~ # auto-mark-install-from-source emulators/virtualbox-ose-kmod kbi root@mowa219-gjp4-8570p-freebsd:~ # auto-mark-install-from-source graphics/gpu-firmware-radeon-kmod@btc kbi /usr/ports/graphics/gpu-firmware-radeon-kmod@btc: No such port. root@mowa219-gjp4-8570p-freebsd:~ # auto-mark-install-from-source graphics/gpu-firmware-radeon-kmod@sumo kbi /usr/ports/graphics/gpu-firmware-radeon-kmod@sumo: No such port. root@mowa219-gjp4-8570p-freebsd:~ # auto-mark-install-from-source graphics/gpu-firmware-radeon-kmod@turks kbi /usr/ports/graphics/gpu-firmware-radeon-kmod@turks: No such port. root@mowa219-gjp4-8570p-freebsd:~ # Specifically: I'd like to _not_ mark graphics/gpu-firmware-radeon-kmod (to not waste time building the entire collection). <https://www.freshports.org/graphics/gpu-firmware-kmod/#requiredrun>
Thanks for the heads-up. I'll look into implementing this feature ASAP.
Try the latest WIP port: https://github.com/outpaddling/auto-admin Seems the user MUST select a flavor in the case of gpu-firmware-radeon-kmod, or it will just arbitrarily default to aruba. We should probably put some thought into how this should all work before committing.
(In reply to Jason W. Bacon from comment #2) Flavors have been in the ports tree for a long time now.
(In reply to Emmanuel Vadot from comment #3) I'm aware of that. The question is how flavors should be handled in a case like gpu-firmware-radeon-kmod. As I pointed out, it defaults to the aruba flavor out of about 3 dozen. This only makes sense for the small fraction of users who want aruba and nothing else.