All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Nyström" <daniel.nystrom@timeterminal.se>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Developers Meeting
Date: Tue, 12 Feb 2013 16:57:27 +0100	[thread overview]
Message-ID: <CAHQn0kh_8=seM=OybRGC--XY1wYFnhnB7Mts4Y+it1AWMqRgcw@mail.gmail.com> (raw)
In-Reply-To: <20130212151823.6f38a844@skate>

On Tue, Feb 12, 2013 at 3:18 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Dear Daniel Nystr?m,
> On Tue, 12 Feb 2013 15:14:37 +0100, Daniel Nystr?m wrote:
>> According to the announcement of udev and systemd being merged, they
>> claimed udev would still be able to be build independently (although
>> through the systemd source tree of course). I requested some info
>> regarding the D-Bus dependency in #systemd and here is the dialog:
>>
>> < speakman> Just heard about udev and systemd merging. And it seems
>> like udev can still be compiled individually although from the same
>> source tree as systemd. But how about it's DBus dependency - will
>> "udev" compile without D-Bus libraries?
>> < ssuominen> speakman: yes, but you have to call specific Makefile.am
>> targets individually... and set environment flags DBUS_CFLAGS=' ' and
>> DBUS_LIBS='
>>                    ' to get past the ./configure check
>> < ssuominen> speakman: gentoo is packaging udev like that, and ebuilds
>> are mostly bash, you could take look at the rather complex setup from
>> the ebuild
>
> Interesting, thanks for asking about this topic.
>
> Note that there was an effort last year to make this easier:
> http://comments.gmane.org/gmane.linux.hotplug.devel/17478. But it
> doesn't seem to have been merged, and the systemd maintainers don't
> think building D-Bus is a problem:
> http://lists.freedesktop.org/archives/systemd-devel/2012-June/005516.html.

That's one sad attitude by the developers. Looks like we're on our own here.

>> Regarding Buildroot I assume dbus and systemd will merge into one
>> single package. Are there anything preventing "systemd" from being
>> "optional" and depend on D-Bus only when enabled?
>
> Why would systemd and dbus would merge into one single package? Are you
> sure you didn't confuse with "systemd and udev would merge into one
> single package" ?

That's my typo, sorry.

  reply	other threads:[~2013-02-12 15:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 23:42 [Buildroot] Report from the Buildroot Developers Meeting Thomas Petazzoni
2013-02-12 10:30 ` Stephan Hoffmann
2013-02-12 10:36   ` Thomas Petazzoni
2013-02-12 11:49     ` Stephan Hoffmann
2013-02-12 11:53       ` Thomas Petazzoni
2013-02-12 11:55   ` Stefan Fröberg
2013-02-12 14:14 ` Daniel Nyström
2013-02-12 14:18   ` Thomas Petazzoni
2013-02-12 15:57     ` Daniel Nyström [this message]
2013-02-13 18:55 ` Yann E. MORIN
2013-02-13 19:54   ` Thomas Petazzoni
2013-02-14 14:25   ` [Buildroot] Google Summer of Code 2013 Thomas Petazzoni
2013-03-03 13:43     ` Thomas Petazzoni
2013-03-03 17:29       ` Thomas De Schampheleire
2013-03-03 17:51       ` Stephan Hoffmann
2013-03-03 18:26         ` Thomas Petazzoni
2013-03-05  6:25           ` Arnout Vandecappelle
2013-03-05 18:32             ` Thomas Petazzoni
2013-03-06  8:57             ` Jérôme Pouiller

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='CAHQn0kh_8=seM=OybRGC--XY1wYFnhnB7Mts4Y+it1AWMqRgcw@mail.gmail.com' \
    --to=daniel.nystrom@timeterminal.se \
    --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 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.