From: Daniel Mack <zonque@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Add package connman
Date: Tue, 06 Dec 2011 00:20:24 +0100 [thread overview]
Message-ID: <4EDD51B8.5050705@gmail.com> (raw)
In-Reply-To: <87bormsjcz.fsf@macbook.be.48ers.dk>
On 12/06/2011 12:13 AM, Peter Korsgaard wrote:
>>>>>> "Daniel" == Daniel Mack <zonque@gmail.com> writes:
>
> Hi,
>
> >> What about installing an initscript? I see there's an example init
> >> script in the connman sources, but that doesn't seem directly applicable
> >> to our busybox based system.
>
> Daniel> Yes, I can write one up.
>
> Great, thanks.
>
> Daniel> Yes, this is the reason why I added resolver support to uClibc some
> Daniel> months back, and all the stuff in upstream now.
>
> >> I don't like to add it if doesn't work with uClibc based toolchains.
>
> Daniel> Well, it does, if you enable UCLIBC_HAS_RESOLVER_SUPPORT. What about
> Daniel> adding a dependency for that? If people want to have connman, they have
> Daniel> to manually select this feature and rebuild their uClibc. Does that
> Daniel> sound ok?
>
> In concept, yes - But as the RESOLVER_SUPPORT isn't in any release yet,
> it becomes a bit more tricky. We can backport the changes to 0.9.32, but
> existing binary toolchains and ctng (unless Yann agrees and we also
> backport to there) stuff will fail.
In a previous discussion on this list I was asking about just this, and
back then you agreed we could depend on BR2_UCLIBC_VERSION_SNAPSHOT in
such a case until there's a new release.
> I'll take a look at it.
Ok, great. I'll post a new version with the discussed topics and leave
the decision of how to handle the toolchain deps to you. Is that ok for you?
Daniel
next prev parent reply other threads:[~2011-12-05 23:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 12:53 [Buildroot] [PATCH] Add package connman Daniel Mack
2011-12-05 13:00 ` Baruch Siach
2011-12-05 13:15 ` [Buildroot] [PATCH v2] " Daniel Mack
2011-12-05 14:37 ` Peter Korsgaard
2011-12-05 15:01 ` Baruch Siach
2011-12-05 15:02 ` Daniel Mack
2011-12-05 15:29 ` Peter Korsgaard
2011-12-05 17:26 ` Daniel Mack
2011-12-05 17:30 ` [Buildroot] [PATCH v3] " Daniel Mack
2011-12-05 22:18 ` Peter Korsgaard
2011-12-05 23:07 ` Daniel Mack
2011-12-05 23:13 ` Peter Korsgaard
2011-12-05 23:20 ` Daniel Mack [this message]
2011-12-05 23:23 ` Peter Korsgaard
2011-12-05 23:27 ` [Buildroot] [PATCH v4] " Daniel Mack
2011-12-07 19:25 ` Peter Korsgaard
2011-12-05 19:20 ` [Buildroot] [PATCH v2] " Thomas Petazzoni
2011-12-05 19:32 ` Daniel Mack
2011-12-05 19:21 ` Thomas Petazzoni
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=4EDD51B8.5050705@gmail.com \
--to=zonque@gmail.com \
--cc=buildroot@busybox.net \
/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