From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: Using the OpenEmbedded metadata to build Linux Distributions
<openembedded-devel@openembedded.org>
Subject: RFC: splitting deploy/ipk into subarchs
Date: Mon, 19 Feb 2007 12:18:49 +0100 [thread overview]
Message-ID: <45D98799.1080309@dominion.kabel.utwente.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
When using multimachine and ipkg deploy/ipk gets awfully crowded after a while. I want to
propose sorting it by subarch. Attached is a patch that adds support for that to
rootfs_ipk.bbclass.
What do you think about that?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFF2YeZMkyGM64RGpERAjYCAJ9nBjdpcvTlvijaQ7o/UlZGWg68tgCdHw4m
IzGLM3yx+X9k/ZgMo+WqT6E=
=N6sc
-----END PGP SIGNATURE-----
[-- Attachment #2: rootfs-ipk-with-sorted-deploy.patch --]
[-- Type: text/x-patch, Size: 1579 bytes --]
#
# old_revision [bc83c51286e87a2b8aa3f79f074cadc05dedb7de]
#
# patch "classes/rootfs_ipk.bbclass"
# from [7824b4ee6ac7524e12d7411575e8bbf4b8a9d321]
# to [016f168e95ecc8150984cc48a14ecbd73a5fd9ed]
#
============================================================
--- classes/rootfs_ipk.bbclass 7824b4ee6ac7524e12d7411575e8bbf4b8a9d321
+++ classes/rootfs_ipk.bbclass 016f168e95ecc8150984cc48a14ecbd73a5fd9ed
@@ -18,17 +18,26 @@ fakeroot rootfs_ipk_do_rootfs () {
mkdir -p ${IMAGE_ROOTFS}/dev
- if [ -z "${DEPLOY_KEEP_PACKAGES}" ]; then
+ ipkgarchs="${PACKAGE_ARCHS}"
+
+ if [ -z "${DEPLOY_KEEP_PACKAGES}" ]; then
touch ${DEPLOY_DIR_IPK}/Packages
ipkg-make-index -r ${DEPLOY_DIR_IPK}/Packages -p ${DEPLOY_DIR_IPK}/Packages -l ${DEPLOY_DIR_IPK}/Packages.filelist -m ${DEPLOY_DIR_IPK}
- fi
+ if [-e ${DEPLOY_DIR_IPK}/$arch/] ; then
+ touch ${DEPLOY_DIR_IPK}/$arch/Packages
+ ipkg-make-index -r ${DEPLOY_DIR_IPK}/$arch/Packages -p ${DEPLOY_DIR_IPK}/$arch/Packages -l ${DEPLOY_DIR_IPK}/$arch/Packages.filelist -m ${DEPLOY_DIR_IPK}/$arch
+ fi
+ fi
+
mkdir -p ${T}
echo "src oe file:${DEPLOY_DIR_IPK}" > ${T}/ipkg.conf
- ipkgarchs="${PACKAGE_ARCHS}"
priority=1
for arch in $ipkgarchs; do
echo "arch $arch $priority" >> ${T}/ipkg.conf
priority=$(expr $priority + 5)
+ if [-e ${DEPLOY_DIR_IPK}/$arch/Packages] ; then
+ echo "src oe file:${DEPLOY_DIR_IPK}/$arch" >> ${T}/ipkg.conf
+ fi
done
ipkg-cl ${IPKG_ARGS} update
if [ ! -z "${LINGUAS_INSTALL}" ]; then
next reply other threads:[~2007-02-19 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 11:18 Koen Kooi [this message]
2007-02-19 11:59 ` RFC: splitting deploy/ipk into subarchs Marcin Juszkiewicz
2007-02-19 12:30 ` Koen Kooi
2007-02-20 8:19 ` Koen Kooi
2007-02-20 13:48 ` Koen Kooi
2007-02-23 2:26 ` Matthias Hentges
2007-02-23 8:05 ` Koen Kooi
2007-02-24 0:03 ` Matthias Hentges
2007-02-24 11:18 ` Michael Rozdoba
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=45D98799.1080309@dominion.kabel.utwente.nl \
--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.