From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Packaged Staging - 'Current' Status
Date: Fri, 14 Mar 2008 22:44:37 +0100 [thread overview]
Message-ID: <frerk5$fd5$1@ger.gmane.org> (raw)
In-Reply-To: <freb8c$k1p$1@ger.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Koen Kooi schreef:
| Richard Purdie schreef:
| | As has been mentioned, I'm working on integrating packaged staging and
| | its about time I mentioned the current status. I say 'current' as it
| | applies to what I have offline, not what's in OE.dev. I aim to commit
| | some of it tomorrow but I also have some changes which should first be
| | discussed, more on that below.
| |
| | Basically the current status is good.
|
| There is a small problem with generating the ipkg arch file properly,
| Richard and I are thinking about a solution.
A workaround is to change the staging_helper() method to something like
this:
staging_helper () {
~ # Assemble appropriate ipkg.conf
~ conffile=${PSTAGE_MACHCONFIG}
~ mkdir -p ${DEPLOY_DIR_PSTAGE}/pstaging_lists
~ if [ ! -e $conffile ]; then
rm $conffile
fi
~ ipkgarchs="${BUILD_ARCH} all any noarch ${TARGET_ARCH}
${PACKAGE_ARCHS} ${PACKAGE_EXTRA_ARCHS} ${MACHINE}"
~ priority=1
~ for arch in $ipkgarchs; do
~ echo "arch $arch $priority" >> $conffile
~ priority=$(expr $priority + 5)
~ done
}
Attentive readers will notice that ${TARGET_ARCH} doesn't always hold
the value we want.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH2vHFMkyGM64RGpERAu0KAKCyiD1o1JGKipSrvY7Dt6BPYqovxACgkxei
KbZn4Mb+OZXJAP84Ra6Uo+s=
=UR5q
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-03-14 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 21:33 Packaged Staging - 'Current' Status Richard Purdie
2008-03-13 22:06 ` Koen Kooi
2008-03-13 23:21 ` Richard Purdie
2008-03-14 12:11 ` Koen Kooi
2008-03-14 17:05 ` Koen Kooi
2008-03-14 21:44 ` Koen Kooi [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='frerk5$fd5$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.