From: "Michal Vu" <saigon-tech@tuta.io>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: x11-misc/ly/
Date: Tue, 13 Aug 2024 14:58:02 +0000 (UTC) [thread overview]
Message-ID: <1723561056.7d5a0d1ceb7a5f2bcee79a96c93677f095d454a4.saigon-tech@gentoo> (raw)
commit: 7d5a0d1ceb7a5f2bcee79a96c93677f095d454a4
Author: Michal Vu <saigon-tech <AT> tuta <DOT> io>
AuthorDate: Tue Aug 13 14:57:23 2024 +0000
Commit: Michal Vu <saigon-tech <AT> tuta <DOT> io>
CommitDate: Tue Aug 13 14:57:36 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=7d5a0d1c
x11-misc/ly: Fixing hprefixify of nonexistent wsetup.sh and xsetup.sh files, only setup.sh is in git version
Signed-off-by: Michal Vu <saigon-tech <AT> tuta.io>
x11-misc/ly/ly-9999.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-misc/ly/ly-9999.ebuild b/x11-misc/ly/ly-9999.ebuild
index 9b84da7ce..a0a1dcdaf 100644
--- a/x11-misc/ly/ly-9999.ebuild
+++ b/x11-misc/ly/ly-9999.ebuild
@@ -175,7 +175,7 @@ src_unpack() {
src_prepare(){
default
# Adjusting absolute paths in the following files to use Gentoo's ${EPREFIX}
- hprefixify "${RES}/config.ini" "${RES}/xsetup.sh" "${RES}/wsetup.sh"
+ hprefixify "${RES}/config.ini" "${RES}/setup.sh"
}
src_compile() {
next reply other threads:[~2024-08-13 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 14:58 Michal Vu [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-02 16:22 [gentoo-commits] repo/proj/guru:dev commit in: x11-misc/ly/ Andre
2024-08-23 10:40 Eric Joldasov
2024-08-13 9:12 Michal Vu
2024-08-13 8:43 Michal Vu
2024-08-13 0:36 Lucio Sauer
2024-08-11 15:56 Michal Vu
2024-08-11 15:41 Michal Vu
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=1723561056.7d5a0d1ceb7a5f2bcee79a96c93677f095d454a4.saigon-tech@gentoo \
--to=saigon-tech@tuta.io \
--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