From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/2] udisks: bump to version 1.0.5
Date: Wed, 2 Sep 2015 12:14:29 +0200 [thread overview]
Message-ID: <20150902121429.2829a9e5@free-electrons.com> (raw)
In-Reply-To: <20150902101033.GY17874@tarshish>
Hello,
On Wed, 2 Sep 2015 13:10:34 +0300, Baruch Siach wrote:
> Hi Vincent,
>
> On Wed, Sep 02, 2015 at 11:05:48AM +0100, Vicente Olivert Riera wrote:
> > +ifeq ($(BR2_PACKAGE_SYSTEMD),y)
> > +UDISKS_CONF_OPTS += libgudev
> > +endif
>
> So libgudev is not even an optional dependency when there is no systemd?
No.
libgudev used to be provided by udev. Then udev was merged in systemd.
Then libgudev was taken out of systemd, and made a separate project.
So:
* If you're using systemd as the udev provider, and you need libgudev,
then you must use the libgudev package.
* If you're using eudev as the udev provider, and you need libgudev,
you have nothing to do, because libgudev is still provided by eudev
(it hasn't been removed of it, like it was done in systemd).
So, libgudev is used in both cases (systemd or not), but it's simply
either provided by the libgudev package (systemd case) or by the udev
implementation itself (eudev case).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-02 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 10:05 [Buildroot] [PATCHv2 1/2] udisks: bump to version 1.0.5 Vicente Olivert Riera
2015-09-02 10:05 ` [Buildroot] [PATCHv2 2/2] udisks: fix build with newer glibc versions Vicente Olivert Riera
2015-09-02 10:10 ` [Buildroot] [PATCHv2 1/2] udisks: bump to version 1.0.5 Baruch Siach
2015-09-02 10:14 ` Thomas Petazzoni [this message]
2015-09-02 10:21 ` Baruch Siach
2015-09-02 10:25 ` Vicente Olivert Riera
2015-09-02 10:14 ` Vicente Olivert Riera
2015-09-02 10:27 ` Baruch Siach
2015-09-02 10:29 ` Vicente Olivert Riera
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=20150902121429.2829a9e5@free-electrons.com \
--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