All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: DEPLOY_DIR and package_stagefile_shell
Date: Thu, 20 Oct 2011 16:55:23 -0400	[thread overview]
Message-ID: <20111020205523.GT26170@denix.org> (raw)
In-Reply-To: <CAFu+nvF2BM344-+5wHCobJshpU=TtuaxD0_WR2CPisNSev0pnQ@mail.gmail.com>

On Wed, Oct 19, 2011 at 05:39:45PM -0400, George C. Huntington, III wrote:
> It appears that if you override DEPLOY_DIR to make the DEPLOY directory
> outside of TMPDIR, then recipes that call package_stagefile_shell fail. the
> sed magic in package_stagefile_shell assumes that the path will be in
> TMPDIR.  Should the package_stagefile_shell be fixed, or should the recipes
> that call it with ${DEPLOY_DIR_IMAGE} be changed.  the u-boot.inc and the
> linux.inc have this problem.

Well, it's an old issue - I first faced it over 3 years ago[1]. I had it 
"fixed" or worked around, by modifying the sed magic. Then it got broken again 
and there wasn't any good fixes available since then. That's the way packaged 
staging works, as pstage had to be relative to deploy dir, which both reside 
in TMPDIR by default.

At one point I even disabled packaged staging in Arago in order to allow 
re-defining DEPLOY_DIR, but later on it got mandated and I just gave in to not 
being able to move DEPLOY_DIR outside of TMPDIR. :)

Either way it's a moot point now with oe-core and shared state...

[1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/19300

-- 
Denys



  reply	other threads:[~2011-10-20 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 21:39 DEPLOY_DIR and package_stagefile_shell George C. Huntington, III
2011-10-20 20:55 ` Denys Dmytriyenko [this message]
2011-10-20 21:11   ` George C. Huntington, III
2011-10-20 23:07     ` Khem Raj

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=20111020205523.GT26170@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@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 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.