Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] What to do about systemd/udev/eudev?
Date: Wed, 6 Mar 2013 09:24:24 +0100	[thread overview]
Message-ID: <20130306092424.52b72106@skate> (raw)
In-Reply-To: <5136F5C4.6070300@mind.be>

Dear Arnout Vandecappelle,

On Wed, 06 Mar 2013 08:52:36 +0100, Arnout Vandecappelle wrote:
> > Also, Olivier's patch doesn't update all the packages that depend on
> > udev so that they can either depend on the old udev, or systemd.
> 
>   Yes, that's what Olivier's patch does: packages that depend on udev 
> will use the old udev, not the systemd udev.
> 
>   Hm, just now I realized that that means that you get two udevs when 
> using systemd...

Yeah, yes this is what I meant by "Olivier's patch doesn't update all
the packages that depend on udev so that they can either depend on the
old udev, or systemd."

> OK, so this is not really the way to go :-(

Well, it might be the way to go, but it needs a bit more work.

We can make a udev-virtual package, or whatever the name, that will
depend on the old udev or systemd.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-03-06  8:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 12:09 [Buildroot] [PATCH 1/1] Updated systemd to version 197 Olivier Schonken
2013-03-03 18:54 ` [Buildroot] What to do about systemd/udev/eudev? Thomas Petazzoni
2013-03-04 10:16   ` Kevin Chadwick
2013-03-04 10:53     ` Lionel Orry
2013-03-04 18:12       ` Stefan Fröberg
2013-03-04 18:21         ` Thomas Petazzoni
2013-03-04 18:25           ` Stefan Fröberg
2013-03-04 18:30             ` Thomas Petazzoni
2013-03-05 18:08               ` Stefan Fröberg
2013-03-05 18:51                 ` Thomas Petazzoni
2013-03-05  8:21           ` Rob Landley
2013-03-05 15:04             ` Charles Krinke
2013-03-05 18:15               ` Thomas Petazzoni
2013-03-06  4:22               ` Rob Landley
2013-03-04 18:37         ` Baruch Siach
2013-03-04 19:08           ` Stefan Fröberg
2013-03-04 19:30             ` Peter Korsgaard
2013-03-05  8:24           ` Rob Landley
2013-03-05  6:40     ` Arnout Vandecappelle
2013-03-05 18:55       ` Thomas Petazzoni
2013-03-06  7:52         ` Arnout Vandecappelle
2013-03-06  8:24           ` Thomas Petazzoni [this message]
2013-03-06  8:40             ` Arnout Vandecappelle
2013-03-04 19:31   ` Peter Korsgaard
2013-03-04 19:52     ` Kevin Chadwick
2013-03-04 20:14       ` Thomas Petazzoni
2013-03-04 19:47   ` Attila Kinali
2013-03-04 20:17     ` Thomas Petazzoni
2013-03-05  9:53       ` Attila Kinali
2013-03-05 18:19         ` Thomas Petazzoni
2013-03-05 18:37           ` Stefan Fröberg
2013-03-07 18:45 ` [Buildroot] [PATCH 1/1] Updated systemd to version 197 Stefan Fröberg
2013-03-07 19:20   ` Stefan Fröberg

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=20130306092424.52b72106@skate \
    --to=thomas.petazzoni@free-electrons.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