From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: sed dependency
Date: Mon, 25 Oct 2010 14:35:36 +0200 [thread overview]
Message-ID: <4CC57998.9080204@opendreambox.org> (raw)
In-Reply-To: <AANLkTimR4TEOwVmWDsvL+WJboq+1qdRssKedS+iiVE9J@mail.gmail.com>
On 10/24/2010 08:53 PM, Frans Meulenbroeks wrote:
> 2010/10/24 Chris Larson <clarson@kergoth.com>:
>> If something is covered by posix / SuSv3, I see no need to use a -native.
>> We have to expect a certain amount of sanity in our build environment. For
>> specific non-portable usages, those should certainly be fixed to not use
>> that functionality, to use some form of sanitizing wrapper, or to depend on
>> the gnu tool specifically via -native, imo.
>> --
> Seems like a good plan to me. Guess then we should reject Andreas's patch.
I've removed the patch from my queue. Because sed is listed as a
prerequisite on http://wiki.openembedded.net/index.php/OEandYourDistro
it really seems to be wrong to depend on sed-native. Maybe it should be
added to sanity.bbclass.
> for the record: this are the recipes that DEPEND on sed-native
>
> libgc/libgc_6.5.bb:DEPENDS = "sed-native"
> libgc/libgc_6.7.bb:DEPENDS = "sed-native"
> meta/canadian-sdk.bb:DEPENDS = "opkg-native ipkg-utils-native
> fakeroot-native sed-native zip-native"
> meta/meta-toolchain.bb:DEPENDS = "opkg-native ipkg-utils-native
> fakeroot-native sed-native"
> opensync/libsyncml_0.4.0.bb:DEPENDS = "sed-native wbxml2 libsoup
> libxml2 bluez-libs openobex"
> opensync/libsyncml_0.4.6.bb:DEPENDS = "sed-native wbxml2 libsoup
> libxml2 bluez-libs openobex"
> opensync/libsyncml_svn.bb:DEPENDS = "sed-native wbxml2 libsoup libxml2
> bluez-libs openobex"
> rpm/rpm_4.4.2.3.bb:DEPENDS = "zlib beecrypt file popt python sed-native"
>
> No idea if they really should depend on it.
I guess not.
Regards,
Andreas
prev parent reply other threads:[~2010-10-25 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 12:00 sed dependency Frans Meulenbroeks
2010-10-24 18:10 ` Chris Larson
2010-10-24 18:53 ` Frans Meulenbroeks
2010-10-25 12:35 ` Andreas Oberritter [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=4CC57998.9080204@opendreambox.org \
--to=obi@opendreambox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox