All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org
Cc: "Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Christian Lindig" <christian.lindig@citrix.com>,
	"David Scott" <dave@recoil.org>
Subject: Re: [PATCH v2 4/4] tools: replace @xxx@ markers at build time
Date: Fri, 14 Nov 2025 14:03:18 +0100	[thread overview]
Message-ID: <b2983c1d-03dc-485e-90ec-b668b85a25be@suse.com> (raw)
In-Reply-To: <d558864b-baa7-4262-9336-1f3362d7924b@citrix.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1372 bytes --]

On 14.11.25 12:54, Andrew Cooper wrote:
> On 14/11/2025 11:32 am, Juergen Gross wrote:
>> diff --git a/tools/hotplug/FreeBSD/Makefile b/tools/hotplug/FreeBSD/Makefile
>> index a6552c9884..8de923781c 100644
>> --- a/tools/hotplug/FreeBSD/Makefile
>> +++ b/tools/hotplug/FreeBSD/Makefile
>> @@ -51,3 +55,4 @@ clean:
>>   
>>   .PHONY: distclean
>>   distclean: clean
>> +	rm -rf $(IN_FILES)
> 
> In addition to the points in patch 2, can we use $(RM) (which includes
> -f IIRC) when adding these.  None of the generated files are
> directories, so the -r wants dropping.

Okay.

> 
> But again, this is far nicer than v1 overall.
> 
>> diff --git a/tools/hotplug/Linux/Makefile b/tools/hotplug/Linux/Makefile
>> index 9a7b3a3515..6fcf84a6f4 100644
>> --- a/tools/hotplug/Linux/Makefile
>> +++ b/tools/hotplug/Linux/Makefile
>> @@ -37,7 +44,7 @@ uninstall: uninstall-initd uninstall-scripts subdirs-uninstall
>>   
>>   # See docs/misc/distro_mapping.txt for INITD_DIR location
>>   .PHONY: install-initd
>> -install-initd:
>> +install-initd: $(IN_FILES)
>>   	$(INSTALL_DIR) $(DESTDIR)$(INITD_DIR)
>>   	$(INSTALL_DIR) $(DESTDIR)$(SYSCONFIG_DIR)
>>   	$(INSTALL_DIR) $(DESTDIR)$(LIBEXEC_BIN)
> 
> Hmm.  Logically, generating the files should be part of the build step,
> not the install step.

Agreed. Will change this.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

      reply	other threads:[~2025-11-14 13:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 11:32 [PATCH v2 0/4] configure: reduce number of files created Juergen Gross
2025-11-14 11:32 ` [PATCH v2 1/4] build: add make macro for making file from file.in Juergen Gross
2025-11-14 11:42   ` Andrew Cooper
2025-11-14 12:54     ` Jürgen Groß
2025-11-17 12:24       ` Jan Beulich
2025-11-17 12:30         ` Andrew Cooper
2025-11-17 12:51           ` Jürgen Groß
2025-11-17 12:37         ` Jürgen Groß
2025-11-17 12:51           ` Jan Beulich
2025-11-17 13:03             ` Jürgen Groß
2025-11-17 12:29   ` Jan Beulich
2025-11-17 12:48     ` Jürgen Groß
2025-11-17 12:54       ` Jan Beulich
2025-11-17 13:10         ` Jürgen Groß
2025-11-17 14:05           ` Jan Beulich
2025-11-14 11:32 ` [PATCH v2 2/4] docs: replace @xxx@ markers at build time Juergen Gross
2025-11-14 11:40   ` Andrew Cooper
2025-11-14 13:00     ` Jürgen Groß
2025-11-17 12:33       ` Jan Beulich
2025-11-17 12:55         ` Jürgen Groß
2025-11-17 13:00           ` Jan Beulich
2025-11-17 13:17             ` Jürgen Groß
2025-11-17 14:06               ` Jan Beulich
2025-11-14 11:32 ` [PATCH v2 3/4] config: remove unused paths from config/Paths.mk.in Juergen Gross
2025-11-14 11:47   ` Andrew Cooper
2025-11-14 13:00     ` Jürgen Groß
2025-11-14 11:32 ` [PATCH v2 4/4] tools: replace @xxx@ markers at build time Juergen Gross
2025-11-14 11:54   ` Andrew Cooper
2025-11-14 13:03     ` Jürgen Groß [this message]

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=b2983c1d-03dc-485e-90ec-b668b85a25be@suse.com \
    --to=jgross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=christian.lindig@citrix.com \
    --cc=dave@recoil.org \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --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.