From: Matthias Hentges <oe@hentges.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: splitting deploy/ipk into subarchs
Date: Fri, 23 Feb 2007 03:26:04 +0100 [thread overview]
Message-ID: <1172197564.5203.11.camel@localhost.localdomain> (raw)
In-Reply-To: <45DAFC38.40000@dominion.kabel.utwente.nl>
Am Dienstag, den 20.02.2007, 14:48 +0100 schrieb Koen Kooi:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Koen Kooi schreef:
>
> > Marcin and I merged a slightly different version of this today.
>
> As some people found out, their upload scripts broke with this change. I'm sorry that
> happened, but those scripts are more easily fixed than ipkg-utils :(
> Due to bug in ipkg-utils being I haven't been using a straight rsync for a while now, so
> for the curious:
Why not make this change optional via a variable
(ie: SPLIT_DEPLOYDIR_IPK = -1 to turn it off) ?
The current version breaks local OE feeds and requires needless
post-processing.
A slugos deploy dir looks like this now:
all
armv5te
i686
ixp4xxle
I honestly don't see any advantage to the previous mode of operation. If
it is needed for unique situations like the rare case of a multi-machine
build, it should be off by default and - by all means - optional.
My 2 cents
--
Matthias Hentges
next prev parent reply other threads:[~2007-02-23 2:27 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
2007-02-20 8:19 ` Koen Kooi
2007-02-20 13:48 ` Koen Kooi
2007-02-23 2:26 ` Matthias Hentges [this message]
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=1172197564.5203.11.camel@localhost.localdomain \
--to=oe@hentges.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox