xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org, "Vadim A. Misbakh-Soloviov" <mva@mva.name>
Subject: Re: [Patch V3 3/3] Fixed policy Makefile with Ian Campbell advice:
Date: Tue, 30 Jul 2013 10:36:54 -0400	[thread overview]
Message-ID: <51F7CF86.1050907@tycho.nsa.gov> (raw)
In-Reply-To: <1375190173.32691.6.camel@kazak.uk.xensource.com>

On 07/30/2013 09:16 AM, Ian Campbell wrote:
> On Tue, 2013-07-30 at 16:34 +0400, Vadim A. Misbakh-Soloviov wrote:
>> From: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
>>
>> 30.07.2013 13:51, Ian Campbell wrote:
>>> I think it would be a bit less surprising for drive by patchers etc to
>>> remove the DESTDIR from POLICY_LOADPATH and add it to the install
>>> target, which is the usual way to do things. Up to you/Vadim though.
>>
>> Signed-off-by: Vadim A. Misbakh-Soloviov <mva@mva.name>
>
> Looks good to me, I'll give Daniel a chance to object though.
>
> Ian.

Also looks good to me. It ends up being $(DESTDIR)//boot, but that's
rather harmless.

Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>

I have already acked patch 1; if you send additional versions of the series
with these patches, you can add the Acked-by: line below your Signed-off-by:
to reflect this.

>
>> ---
>>   tools/flask/policy/Makefile | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/flask/policy/Makefile b/tools/flask/policy/Makefile
>> index df1e8f3..a1c0f11 100644
>> --- a/tools/flask/policy/Makefile
>> +++ b/tools/flask/policy/Makefile
>> @@ -33,7 +33,7 @@ M4 ?= m4
>>   OUTPUT_POLICY = 24
>>
>>   POLICY_FILENAME = xenpolicy.$(OUTPUT_POLICY)
>> -POLICY_LOADPATH = $(DESTDIR)/boot
>> +POLICY_LOADPATH = /boot
>>
>>   # policy source layout
>>   POLDIR := policy
>> @@ -103,8 +103,8 @@ POLICY_SECTIONS += $(USERS) $(CONSTRAINTS) $(ISID_DEFS)
>>   all: $(POLICY_FILENAME)
>>
>>   install: $(POLICY_FILENAME)
>> -	$(INSTALL_DIR) $(POLICY_LOADPATH)
>> -	$(INSTALL_DATA) $^ $(POLICY_LOADPATH)
>> +	$(INSTALL_DIR) $(DESTDIR)/$(POLICY_LOADPATH)
>> +	$(INSTALL_DATA) $^ $(DESTDIR)/$(POLICY_LOADPATH)
>>
>>   $(POLICY_FILENAME): policy.conf
>>   	$(CHECKPOLICY) $(CHECKPOLICY_PARAM) $^ -o $@
>
>
>


-- 
Daniel De Graaf
National Security Agency

  reply	other threads:[~2013-07-30 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 12:34 [Patch V3 1/3] Fixed flask policy's install path to avoid installing it as '/boot' file Vadim A. Misbakh-Soloviov
2013-07-30 12:34 ` [Patch V3 2/3] Fixed xen-tools makefile to build flask-tools and flask policy only if flask build especially enabled Vadim A. Misbakh-Soloviov
2013-07-30 12:34 ` [Patch V3 3/3] Fixed policy Makefile with Ian Campbell advice: Vadim A. Misbakh-Soloviov
2013-07-30 13:16   ` Ian Campbell
2013-07-30 14:36     ` Daniel De Graaf [this message]
2013-07-31 19:29     ` Vadim A. Misbakh-Soloviov
2013-07-31 19:43       ` Ian Campbell
2013-08-02 16:07 ` [Patch V3 1/3] Fixed flask policy's install path to avoid installing it as '/boot' file Ian Campbell
2013-08-02 17:10   ` Vadim A. Misbakh-Soloviov

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=51F7CF86.1050907@tycho.nsa.gov \
    --to=dgdegra@tycho.nsa.gov \
    --cc=Ian.Campbell@citrix.com \
    --cc=mva@mva.name \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).