From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Anthony PERARD" <anthony@xenproject.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] tools: Add install/uninstall targets to tests/x86_emulator
Date: Thu, 16 May 2024 14:15:37 +0100 [thread overview]
Message-ID: <1c98ba15-fcbf-4fa1-aa0e-39de8bdfb5fa@cloud.com> (raw)
In-Reply-To: <cf8cfb82-7a69-4690-8afb-d971dbe8b7e3@suse.com>
Hi,
On 16/05/2024 12:16, Jan Beulich wrote:
> On 16.05.2024 13:07, Alejandro Vallejo wrote:
>> Bring test_x86_emulator in line with other tests by adding
>> install/uninstall rules.
>>
>> Signed-off-by: Alejandro Vallejo <alejandro.vallejo@cloud.com>
>
> I'd expect such a change to come with a word towards what use the binary has
> on the installed system.
First of all, having some tests installed and some not is highly
confusing (See [1]).
> Imo we should not randomly put binaries in place
> when there's - afaict - absolutely no use for them outside of development
I don't disagree, but that's (imo) a packaging matter. For reference
XenServer has a xen-dom0-tests package for this very purpose, so we can
install it or withhold it at will.
Being able to validate that the development invariants still hold on
whatever machine you happen to be running on is generally a good thing,
I reckon.
Cheers,
Alejandro
==============================
[1] (grepped for the install target in the tests folder)
[snip]
--
./paging-mempool/Makefile:install: all
./paging-mempool/Makefile- $(INSTALL_DIR) $(DESTDIR)$(LIBEXEC_BIN)
./paging-mempool/Makefile- $(INSTALL_PROG) $(TARGET)
$(DESTDIR)$(LIBEXEC_BIN)
--
./xenstore/Makefile:install: all
./xenstore/Makefile- $(INSTALL_DIR) $(DESTDIR)$(LIBEXEC_BIN)
./xenstore/Makefile- $(if $(TARGETS),$(INSTALL_PROG) $(TARGETS)
$(DESTDIR)$(LIBEXEC_BIN))
--
./depriv/Makefile:install: all
./depriv/Makefile- $(INSTALL_DIR) $(DESTDIR)$(LIBEXEC_BIN)
./depriv/Makefile- $(INSTALL_PROG) $(INSTALL_PRIVBIN)
$(DESTDIR)$(LIBEXEC_BIN)
--
./cpu-policy/Makefile:install: all
./cpu-policy/Makefile- $(INSTALL_DIR) $(DESTDIR)$(LIBEXEC_BIN)
./cpu-policy/Makefile- $(if $(TARGETS),$(INSTALL_PROG) $(TARGETS)
$(DESTDIR)$(LIBEXEC_BIN))
[snip]
next prev parent reply other threads:[~2024-05-16 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 11:07 [PATCH] tools: Add install/uninstall targets to tests/x86_emulator Alejandro Vallejo
2024-05-16 11:16 ` Jan Beulich
2024-05-16 13:15 ` Alejandro Vallejo [this message]
2024-05-16 11:35 ` Roger Pau Monné
2024-05-16 12:29 ` Alejandro Vallejo
2024-05-16 12:37 ` Jan Beulich
2024-05-16 14:46 ` Alejandro Vallejo
2024-05-21 6:13 ` Jan Beulich
2025-05-20 21:02 ` Andrew Cooper
2025-05-20 22:48 ` Stefano Stabellini
2025-05-21 7:06 ` Jan Beulich
2025-05-30 14:18 ` Andrew Cooper
2025-05-26 15:38 ` Anthony PERARD
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=1c98ba15-fcbf-4fa1-aa0e-39de8bdfb5fa@cloud.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony@xenproject.org \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.