aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIonen Wolkens <ionen@gentoo.org>2023-01-15 20:22:10 -0500
committerIonen Wolkens <ionen@gentoo.org>2023-01-15 20:27:17 -0500
commit01585f91d19a9979e564ecb66bc108bc16da76f6 (patch)
tree798b55d96364471da1ce88de538a474633fba926
parentv2.0.2 (diff)
downloadeselect-wine-01585f91d19a9979e564ecb66bc108bc16da76f6.tar.gz
eselect-wine-01585f91d19a9979e564ecb66bc108bc16da76f6.tar.bz2
eselect-wine-01585f91d19a9979e564ecb66bc108bc16da76f6.zip
wine.eselect: adjust portage PATH comment
Gave this another look given PATH handling changes in >=portage-3.0.44, and the workaround is "nearly" unnecessary now but still triggers (at least) on first merge of eselect-wine while PATH has not yet been updated once yet. May possibly be other cases where it's noisy, so decided to leave it alone beside a minor comment update. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
-rw-r--r--wine.eselect2
1 files changed, 1 insertions, 1 deletions
diff --git a/wine.eselect b/wine.eselect
index 46610ea..e8ce744 100644
--- a/wine.eselect
+++ b/wine.eselect
@@ -30,7 +30,7 @@ wine-run() {
# try to warn about about missing PATH, but stay quiet with doas/sudo
# given may be using a temporary secure PATH (also skip with update
- # given PATH is not updated when ran from ebuilds in pkg_postinst)
+ # as the PATH may not always be updated in ebuild phases yet)
[[ ${PATH} == @(|*:)"${EPREFIX}${WINEETC}/bin"*(/)@(|:*) ||
-v DOAS_USER || -v SUDO_USER || ${1} == wine-update ]] ||
write_warning_msg "'${EPREFIX}${WINEETC}/bin' missing from PATH, may need to run '. ${EROOT}/etc/profile'"