From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: DEPLOY_DIR / packaged staging / persistent toolchains
Date: Tue, 07 Apr 2009 14:49:21 -0400 [thread overview]
Message-ID: <20090407184921.GE11203@denix.org> (raw)
In-Reply-To: <grg59h$e3q$1@ger.gmane.org>
On Tue, Apr 07, 2009 at 08:16:16PM +0200, Koen Kooi wrote:
> On 07-04-09 19:43, Denys Dmytriyenko wrote:
>> if you don't have opkg in your system PATH, you may need to
>> remove opkg packages from pstage to force rebuilding and installing it.
>> Its a
>> chicken and egg problem - opkg-native binary is in .ipk and in order to
>> install and use it you need opkg-native...
>
> That's not true:
>
> PSTAGE_PKGMANAGER = "stage-manager-ipkg"
>
> [..]
>
> pkgmanager = bb.which(path, 'opkg-cl')
> if pkgmanager == "":
> pkgmanager = bb.which(path, 'ipkg-cl')
> if pkgmanager != "":
> bb.data.setVar("PSTAGE_PKGMANAGER", pkgmanager, d)
>
>
> stage-manager-ipkg is a shell script (flashback to the original ipkg
> implementation), which will get used till opkg-cl is found in $PATH.
Hmm, good to know - thanks! I wonder why it doesn't always work, as reported
on irc? The workaround so far was to delete the opkg package from pstage...
--
Denys
next prev parent reply other threads:[~2009-04-07 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 10:12 DEPLOY_DIR / packaged staging / persistent toolchains Michael 'Mickey' Lauer
2009-04-07 17:43 ` Denys Dmytriyenko
2009-04-07 18:16 ` Koen Kooi
2009-04-07 18:49 ` Denys Dmytriyenko [this message]
2009-04-07 19:10 ` Koen Kooi
2009-04-07 22:39 ` Michael 'Mickey' Lauer
2009-04-07 23:18 ` Denys Dmytriyenko
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=20090407184921.GE11203@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.