$(use_with secure-path secure-path ${SECURE_PATH}) --with-secure-path="${SECURE_PATH}" wtf is this. if you're going to put a USE flag, at least make it work properly. IMO it's dumb to differ from upstream default and all other distros unnecessarily, and I know it's easy to turn off, but come on.
There's no need to be rude. Seems like a simple mistake.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=494b140bb12a2b2cccbea5bf46c6a7cac60e5869 commit 494b140bb12a2b2cccbea5bf46c6a7cac60e5869 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2019-11-08 15:43:18 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2019-11-08 15:43:18 +0000 app-admin/sudo: fix secure-path USE flag Closes: https://bugs.gentoo.org/699620 Package-Manager: Portage-2.3.78_p15, Repoman-2.3.17_p111 Signed-off-by: Mike Gilbert <floppym@gentoo.org> app-admin/sudo/sudo-1.8.27-r1.ebuild | 3 +-- app-admin/sudo/sudo-1.8.28_p1-r2.ebuild | 3 +-- app-admin/sudo/sudo-1.8.29-r2.ebuild | 3 +-- app-admin/sudo/sudo-9999.ebuild | 3 +-- 4 files changed, 4 insertions(+), 8 deletions(-)
