From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: splitting deploy/ipk into subarchs
Date: Mon, 19 Feb 2007 13:30:04 +0100 [thread overview]
Message-ID: <45D9984C.6090705@dominion.kabel.utwente.nl> (raw)
In-Reply-To: <200702191259.25200.openembedded@hrw.one.pl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marcin Juszkiewicz schreef:
> Dnia poniedziałek, 19 lutego 2007, Koen Kooi napisał:
>
>> 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?
>
> I like this idea. ipkg-make-index is slow enough already.
>
> Attached fixed, tested version of your rootfs_ipk.bbclass change. Also
> added patch to package_ipk.bbclass which will store package in proper
> dir.
Nice
> - echo "src oe file:${DEPLOY_DIR_IPK}" > ${T}/ipkg.conf
This breaks backward compat, could you add that back in?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFF2ZhMMkyGM64RGpERAtwOAJ0d4gxAt3a/XFjsJP+5xFvsapJdswCePBQN
QCZEkVp954PrWVq1QERxVtQ=
=Qtcf
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-02-19 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 11:18 RFC: splitting deploy/ipk into subarchs Koen Kooi
2007-02-19 11:59 ` Marcin Juszkiewicz
2007-02-19 12:30 ` Koen Kooi [this message]
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=45D9984C.6090705@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.