Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package: udev is now provided by systemd or eudev.
Date: Wed, 18 Sep 2013 23:46:57 +0200	[thread overview]
Message-ID: <523A1F51.1090906@mind.be> (raw)
In-Reply-To: <20130918184035.24b2c345@skate>

On 18/09/13 18:40, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
>
> On Wed, 18 Sep 2013 18:04:34 +0200, Arnout Vandecappelle wrote:
>
>>> Right, that's one way of seeing things, indeed. It sounds a bit
>>> convoluted to me, though. When a package A needs a specific feature
>>> from package B (such as gudev), I believe it makes sense for
>>> package B to provide a sub-option that package A can select, rather
>>> than package A having intimate knowledge of the dependencies needed
>>> by package B to enable whatever feature package A needs to have
>>> from package B.
>>
>>    Makes sense, but we probably already have tons of these already. If
>> gudev would have been added in the normal way instead of introducing
>> the all_extras option, then the implementors of network-manager and
>> udisks wouldn't even have noticed that udev had to be compiled in a
>> specific way: since these tools already select libglib2, udev would
>> have been compiled with gudev support.
>
> True.
>
>>    Really, the all-extras is historical accident because a long time
>> ago udev's configure had an EXTRAS=... option in its build commands.
>
> Right. But the extras have more dependencies that just glib2: it also
> depends on hwdata and on acl. Will glib2 be sufficient to get gudev
> built, for use by udisks? Maybe.

  For eudev this doesn't seem to be the case anymore. Or else the patch 
was wrong :-)

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-09-18 21:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 14:01 [Buildroot] [PATCH 1/1] package: udev is now provided by systemd or eudev eric.le.bihan.dev at free.fr
2013-09-06 14:08 ` Eric Le Bihan
2013-09-10 20:24 ` Arnout Vandecappelle
2013-09-17 10:40   ` Eric Le Bihan
2013-09-18  4:45     ` Thomas Petazzoni
2013-09-18  6:52     ` Arnout Vandecappelle
2013-09-17 18:37   ` Thomas Petazzoni
2013-09-18  6:57     ` Arnout Vandecappelle
2013-09-18 15:56       ` Thomas Petazzoni
2013-09-18 16:04         ` Arnout Vandecappelle
2013-09-18 16:40           ` Thomas Petazzoni
2013-09-18 21:46             ` Arnout Vandecappelle [this message]
2013-09-17  5:17 ` Thomas Petazzoni
2013-09-17 12:53   ` Eric Le Bihan
2013-09-17 18:45     ` Thomas Petazzoni
2013-09-18  7:00       ` Arnout Vandecappelle
2013-09-18 15:58         ` Thomas Petazzoni
2013-09-18 16:06           ` Arnout Vandecappelle
2013-09-18 16:41             ` Thomas Petazzoni
2013-09-18 17:34               ` Sagaert Johan
2013-09-18 17:39                 ` Thomas Petazzoni
2013-09-18 18:13                   ` Sagaert Johan
2013-09-18 18:05                 ` [Buildroot] [PATCH 1/1] package: udev is now provided bysystemd " Sagaert Johan
2013-09-18 18:16                   ` 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=523A1F51.1090906@mind.be \
    --to=arnout@mind.be \
    --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