public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/virtiofsd/
Date: Thu, 27 Jul 2023 12:00:54 +0000 (UTC)	[thread overview]
Message-ID: <1690459229.0a38ac0e9f9f4f6b7c0f8fbca13b6ae9256ad6ed.sam@gentoo> (raw)

commit:     0a38ac0e9f9f4f6b7c0f8fbca13b6ae9256ad6ed
Author:     Michal Privoznik <michal.privoznik <AT> gmail <DOT> com>
AuthorDate: Thu Jul 27 10:08:48 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul 27 12:00:29 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0a38ac0e

app-emulation/virtiofsd: Move virtiofsd binary into /usr/libexec

In one of my recent commits I've introduced JSON descriptor file
that libvirt uses when learning about helper binaries
(40-qemu-virtiofsd.json). What I did not realize is that the file
tells libvirt to execute /usr/libexec/virtiofsd while our ebuilds
install the binary under /usr/bin/.

I haven't found a way to tell cargo_src_install where to install
the binary so we have to move it 'manually'.

Bug: https://bugs.gentoo.org/909372
Closes: https://bugs.gentoo.org/911274
Signed-off-by: Michal Privoznik <michal.privoznik <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/32062
Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../virtiofsd/{virtiofsd-1.5.1-r1.ebuild => virtiofsd-1.5.1-r2.ebuild} | 3 +++
 .../virtiofsd/{virtiofsd-1.6.1.ebuild => virtiofsd-1.6.1-r1.ebuild}    | 3 +++
 app-emulation/virtiofsd/virtiofsd-9999.ebuild                          | 3 +++
 3 files changed, 9 insertions(+)

diff --git a/app-emulation/virtiofsd/virtiofsd-1.5.1-r1.ebuild b/app-emulation/virtiofsd/virtiofsd-1.5.1-r2.ebuild
similarity index 97%
rename from app-emulation/virtiofsd/virtiofsd-1.5.1-r1.ebuild
rename to app-emulation/virtiofsd/virtiofsd-1.5.1-r2.ebuild
index a609ac7791fa..9b66f0ea8185 100644
--- a/app-emulation/virtiofsd/virtiofsd-1.5.1-r1.ebuild
+++ b/app-emulation/virtiofsd/virtiofsd-1.5.1-r2.ebuild
@@ -128,6 +128,9 @@ src_unpack() {
 src_install() {
 	cargo_src_install
 
+	mkdir "${ED}/usr/libexec" || die
+	mv "${ED}/usr/"{bin,libexec}/${PN} || die
+
 	# Install 50-qemu-virtiofsd.json but to avoid conflicts with
 	# <app-emulation/qemu-8.0.0 install it under different name. In this case,
 	# smaller number means higher priority, but that's probably what users want

diff --git a/app-emulation/virtiofsd/virtiofsd-1.6.1.ebuild b/app-emulation/virtiofsd/virtiofsd-1.6.1-r1.ebuild
similarity index 97%
rename from app-emulation/virtiofsd/virtiofsd-1.6.1.ebuild
rename to app-emulation/virtiofsd/virtiofsd-1.6.1-r1.ebuild
index bd8fc8dcbfe7..c3d0af907834 100644
--- a/app-emulation/virtiofsd/virtiofsd-1.6.1.ebuild
+++ b/app-emulation/virtiofsd/virtiofsd-1.6.1-r1.ebuild
@@ -130,6 +130,9 @@ src_unpack() {
 src_install() {
 	cargo_src_install
 
+	mkdir "${ED}/usr/libexec" || die
+	mv "${ED}/usr/"{bin,libexec}/${PN} || die
+
 	# Install 50-qemu-virtiofsd.json but to avoid conflicts with
 	# <app-emulation/qemu-8.0.0 install it under different name. In this case,
 	# smaller number means higher priority, but that's probably what users want

diff --git a/app-emulation/virtiofsd/virtiofsd-9999.ebuild b/app-emulation/virtiofsd/virtiofsd-9999.ebuild
index bd8fc8dcbfe7..c3d0af907834 100644
--- a/app-emulation/virtiofsd/virtiofsd-9999.ebuild
+++ b/app-emulation/virtiofsd/virtiofsd-9999.ebuild
@@ -130,6 +130,9 @@ src_unpack() {
 src_install() {
 	cargo_src_install
 
+	mkdir "${ED}/usr/libexec" || die
+	mv "${ED}/usr/"{bin,libexec}/${PN} || die
+
 	# Install 50-qemu-virtiofsd.json but to avoid conflicts with
 	# <app-emulation/qemu-8.0.0 install it under different name. In this case,
 	# smaller number means higher priority, but that's probably what users want


             reply	other threads:[~2023-07-27 12:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 12:00 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-08  1:33 [gentoo-commits] repo/gentoo:master commit in: app-emulation/virtiofsd/ Sam James
2025-01-06  3:32 Sam James
2025-01-06  3:28 Sam James
2024-10-11  2:29 Sam James
2024-10-11  2:29 Sam James
2024-09-23 10:08 Arthur Zamarin
2024-07-07  6:32 Sam James
2024-07-07  6:32 Sam James
2024-04-29 10:36 Joonas Niilola
2024-03-02  5:05 Sam James
2024-01-26  8:57 Sam James
2024-01-26  7:50 Sam James
2024-01-26  7:50 Sam James
2024-01-26  7:50 Sam James
2024-01-26  7:50 Sam James
2024-01-26  7:50 Sam James
2023-09-06  9:06 Sam James
2023-07-28  7:55 Joonas Niilola
2023-07-02 22:39 Sam James
2023-07-02 22:39 Sam James
2023-07-02 22:39 Sam James
2023-04-17 15:04 Matthias Maier
2023-04-17 15:04 Matthias Maier

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=1690459229.0a38ac0e9f9f4f6b7c0f8fbca13b6ae9256ad6ed.sam@gentoo \
    --to=sam@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