From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-eselect/eselect-wine/
Date: Sat, 3 Dec 2022 01:03:34 +0000 (UTC) [thread overview]
Message-ID: <1670029390.77a11023eaa26a4403092173fd81ec6d828d5377.ionen@gentoo> (raw)
commit: 77a11023eaa26a4403092173fd81ec6d828d5377
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 3 00:57:16 2022 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Sat Dec 3 01:03:10 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=77a11023
app-eselect/eselect-wine: use later (95) priority for env.d
Shouldn't(?) have a real impact but it seems wasteful for
its XDG_DATA_DIRS be searched earlier than 90xdg-data-base
(aka >90 will cause it to add wine's after /usr/share).
Also wouldn't want wine's semi-random binaries to have priority,
albeit PATH already typically came last with 60.
(reminder need to `. /etc/profile` to update in current shells)
Bug: https://bugs.gentoo.org/884077
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
.../{eselect-wine-2.0.1.ebuild => eselect-wine-2.0.1-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-eselect/eselect-wine/eselect-wine-2.0.1.ebuild b/app-eselect/eselect-wine/eselect-wine-2.0.1-r1.ebuild
similarity index 99%
rename from app-eselect/eselect-wine/eselect-wine-2.0.1.ebuild
rename to app-eselect/eselect-wine/eselect-wine-2.0.1-r1.ebuild
index 8a665f8d91e8..9970fb76df07 100644
--- a/app-eselect/eselect-wine/eselect-wine-2.0.1.ebuild
+++ b/app-eselect/eselect-wine/eselect-wine-2.0.1-r1.ebuild
@@ -33,7 +33,7 @@ src_install() {
keepdir /etc/eselect/wine
- newenvd - 60${PN} <<-EOF
+ newenvd - 95${PN} <<-EOF
PATH="${EPREFIX}/etc/eselect/wine/bin"
MANPATH="${EPREFIX}/etc/eselect/wine/share/man"
XDG_DATA_DIRS="${EPREFIX}/etc/eselect/wine/share"
next reply other threads:[~2022-12-03 1:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 1:03 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-14 8:00 [gentoo-commits] repo/gentoo:master commit in: app-eselect/eselect-wine/ Ionen Wolkens
2024-07-25 21:49 Ionen Wolkens
2023-08-23 15:41 Ionen Wolkens
2023-08-23 15:41 Ionen Wolkens
2023-08-06 4:32 Ionen Wolkens
2023-07-30 19:29 Ionen Wolkens
2023-07-30 16:18 Ionen Wolkens
2023-03-03 5:26 Ionen Wolkens
2022-12-29 20:29 Ionen Wolkens
2022-12-05 20:46 Ionen Wolkens
2022-12-03 22:40 Ionen Wolkens
2022-12-03 14:08 Ionen Wolkens
2022-12-03 13:52 Ionen Wolkens
2022-12-02 3:18 Ionen Wolkens
2022-12-02 3:18 Ionen Wolkens
2022-11-29 0:27 Ionen Wolkens
2022-11-23 20:39 Ionen Wolkens
2022-11-23 20:39 Ionen Wolkens
2022-11-20 17:12 Ionen Wolkens
2022-11-17 7:53 Ionen Wolkens
2022-11-16 17:01 Ionen Wolkens
2022-11-16 15:02 Ionen Wolkens
2022-10-12 13:47 Ionen Wolkens
2022-10-12 13:47 Ionen Wolkens
2022-10-12 13:47 Ionen Wolkens
2022-08-11 18:41 Nick Sarnie
2022-07-24 8:26 Joonas Niilola
2021-02-07 1:43 Sam James
2017-09-29 3:07 NP Hardass
2017-09-28 22:32 NP Hardass
2017-09-15 6:10 NP Hardass
2017-09-15 6:01 NP Hardass
2017-09-13 23:54 NP Hardass
2017-08-07 14:10 NP Hardass
2017-04-12 1:37 NP Hardass
2017-04-11 6:03 NP Hardass
2017-04-10 17:22 NP Hardass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1670029390.77a11023eaa26a4403092173fd81ec6d828d5377.ionen@gentoo \
--to=ionen@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox