Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [RFC][dizzy][fido][master][PATCH 1/3] rootfs.py: Allow to override postinst-intercepts location
Date: Thu, 10 Sep 2015 09:07:55 -0700	[thread overview]
Message-ID: <55F1AADB.1050604@gmail.com> (raw)
In-Reply-To: <20150904122702.GB2457@jama>

All 3 in master so backporting to Dizzy.

- armin

On 09/04/2015 05:27 AM, Martin Jansa wrote:
> On Fri, Sep 04, 2015 at 02:22:26PM +0200, Martin Jansa wrote:
>> * useful when we need to overlay/extend intercept scripts from oe-core
> 
> 2/3 and 3/3 could be a bit dangerous or controversial (main reason why
> this was sent as RFC), but this one is really useful for us to apply
> these fixes in advance (and without backporting them all to fido and
> dizzy) - so if you agree please merge 1/3 to master, fido and dizzy.
> 
>> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>> ---
>>  meta/lib/oe/rootfs.py | 6 ++++--
>>  1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
>> index c29843b..76950ec 100644
>> --- a/meta/lib/oe/rootfs.py
>> +++ b/meta/lib/oe/rootfs.py
>> @@ -164,6 +164,9 @@ class Rootfs(object):
>>          pre_process_cmds = self.d.getVar("ROOTFS_PREPROCESS_COMMAND", True)
>>          post_process_cmds = self.d.getVar("ROOTFS_POSTPROCESS_COMMAND", True)
>>  
>> +        postinst_intercepts_dir = self.d.getVar("POSTINST_INTERCEPTS_DIR", True)
>> +        if not postinst_intercepts_dir:
>> +            postinst_intercepts_dir = self.d.expand("${COREBASE}/scripts/postinst-intercepts")
>>          intercepts_dir = os.path.join(self.d.getVar('WORKDIR', True),
>>                                        "intercept_scripts")
>>  
>> @@ -173,8 +176,7 @@ class Rootfs(object):
>>  
>>          bb.utils.mkdirhier(self.deploy_dir_image)
>>  
>> -        shutil.copytree(self.d.expand("${COREBASE}/scripts/postinst-intercepts"),
>> -                        intercepts_dir)
>> +        shutil.copytree(postinst_intercepts_dir, intercepts_dir)
>>  
>>          shutil.copy(self.d.expand("${COREBASE}/meta/files/deploydir_readme.txt"),
>>                      self.deploy_dir_image +
>> -- 
>> 2.5.0
>>
> 
> 
> 


  reply	other threads:[~2015-09-10 16:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 12:22 [RFC][PATCH 1/3] rootfs.py: Allow to override postinst-intercepts location Martin Jansa
2015-09-04 12:22 ` [RFC][PATCH 2/3] postinst_intercept: allow to pass variables with spaces Martin Jansa
2015-09-04 12:22 ` [RFC][PATCH 3/3] fontcache: allow to pass extra parameters and environment to fc-cache Martin Jansa
2015-09-10 14:31   ` [PATCHv2] " Martin Jansa
2015-09-29 15:50     ` Martin Jansa
2015-10-14 14:37       ` Martin Jansa
2015-09-04 12:27 ` [RFC][dizzy][fido][master][PATCH 1/3] rootfs.py: Allow to override postinst-intercepts location Martin Jansa
2015-09-10 16:07   ` akuster808 [this message]
2015-09-04 18:56 ` [RFC][PATCH] rootfs.py: show intercept script output in log.do_rootfs Martin Jansa
2015-09-15 16:04 ` [RFC][PATCH 1/3] rootfs.py: Allow to override postinst-intercepts location Joshua Lock

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=55F1AADB.1050604@gmail.com \
    --to=akuster808@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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