Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] wic: fix creation of working directory
Date: Thu,  2 Feb 2017 15:32:56 +0200	[thread overview]
Message-ID: <cover.1486041986.git.ed.bartosh@linux.intel.com> (raw)

Hi,

Changed working directory to be subdirectory of output dir.
This should fix several possible issues:
- current code uses mktemp which doesn't create anything
- default temporary directory is created in /tmp, which can
  cause wic to take long time to move result image as output
  directory can be on another partition
- possible disk space issues due to the /tmp usage

The following changes since commit 7d75fd29296a9c411881b4288bff2e02cb145a25:

  wic: remove syslinux.py (2017-02-01 12:46:17 +0200)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ed/wic/refactoring-10619
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wic/refactoring-10619

Ed Bartosh (3):
  wic: engine: create output dir
  wic: direct: fix creation of work directory
  wic: get rid of image_output_dir variable

 scripts/lib/wic/engine.py                | 3 +++
 scripts/lib/wic/plugins/imager/direct.py | 2 +-
 scripts/wic                              | 6 +-----
 3 files changed, 5 insertions(+), 6 deletions(-)

--
2.1.4



             reply	other threads:[~2017-02-02 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 13:32 Ed Bartosh [this message]
2017-02-02 13:32 ` [PATCH 1/3] wic: engine: create output dir Ed Bartosh
2017-02-02 13:32 ` [PATCH 2/3] wic: direct: fix creation of work directory Ed Bartosh
2017-02-02 13:32 ` [PATCH 3/3] wic: get rid of image_output_dir variable Ed Bartosh

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=cover.1486041986.git.ed.bartosh@linux.intel.com \
    --to=ed.bartosh@linux.intel.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