Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: david.reyna@windriver.com
Subject: Re: [PATCH v2] "Finish" the IMAGE_GEN_DEBUGFS implementation
Date: Fri, 2 Oct 2015 09:57:22 -0500	[thread overview]
Message-ID: <560E9B52.1080101@windriver.com> (raw)
In-Reply-To: <1443797624-183169-1-git-send-email-mark.hatle@windriver.com>

On 10/2/15 9:53 AM, Mark Hatle wrote:
> V2:
> By adjusting the _write_script function (and associated _get_imagecmds) the
> script may optionally pass in a prefix for the generated script.  This solves
> one of the problems in the prior version.  (No more script name collisions.)
> 
> The second issue is that the datastore is used to find various parameters
> (which are different in the DEBUGFS datastore) when doing the final symlink
> generation.
> 
> So we do have to switch (based on the script prefix) which datastore we
> should be using.  (Note, I'm not completely sure that the switch is 'safe',
> so this is an area that should be verified.)

And I verified, it is indeed not safe..

The script name is set by:

        script_name = os.path.join(tempdir, sprefix + "create_image." + type)

So I'd need to exclude the tempdir ($T) in order for the test to be right.. and
even then it probably should be a 'startwith' comparison?

Does this seem right to others?

--Mark

> V1:
> 
> It was noticed today that the IMAGE_GEN_DEBUGFS implementation was not 
> complete.  The version that was merged back in May only contained the 
> filesystem generation pieces, but not the pieces for creating the image
> from that filesystem.
> 
> The code has been tested and is working.  The only thing that I don't 
> particularly like is that the processing code and loop is a duplicate of
> the code that runs just before.  Unfortunately the only way around this
> is to change the way that way the parallel bits are processed to support
> multiple datastores..  (or create "another" function..)
> 
> Any feedback appreciated, but without this the feature is broken!
> 
> Mark Hatle (1):
>   lib/oe/image.py: Add image generation for companion debug filesystem
> 
>  meta/conf/documentation.conf         |  2 ++
>  meta/conf/local.conf.sample.extended |  9 +++++++++
>  meta/lib/oe/image.py                 | 37 +++++++++++++++++++++++++++++++-----
>  3 files changed, 43 insertions(+), 5 deletions(-)
> 



      parent reply	other threads:[~2015-10-02 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 14:53 [PATCH v2] "Finish" the IMAGE_GEN_DEBUGFS implementation Mark Hatle
2015-10-02 14:53 ` [PATCH v2] lib/oe/image.py: Add image generation for companion debug filesystem Mark Hatle
2015-10-02 14:57 ` Mark Hatle [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=560E9B52.1080101@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=david.reyna@windriver.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