Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][meta-oe 3/3] polkit: depends on systemd
Date: Thu, 09 Feb 2012 19:51:29 +0100	[thread overview]
Message-ID: <jh14jj$866$2@dough.gmane.org> (raw)
In-Reply-To: <CAP9ODKpzNm9DCkkWWr0sHaiuWZAKyd37tqFhQzmLY8Vw_qQkOg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 09-02-12 17:14, Otavio Salvador schreef:
> On Thu, Feb 9, 2012 at 14:00, Martin Jansa <martin.jansa@gmail.com>
> wrote:
> 
>> So it's clear that systemd will always be enabled and still easy to 
>> override both with .bbappend?
>> 
> 
> For the current state of polkit it might be better to disable systemd on 
> this, completely. So passing --disable-systemd to autoconf. What do you 
> think?

Well, systemd is the only backend that actually works in our current
metadata, so I'm hesitant to globally disable it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk80FbEACgkQMkyGM64RGpFyNQCfU0ANmYwoxrK4+J8bzMGr8Wy3
J7sAnil8V8UOxuc+p+8zCXszOB8zhbzp
=/tbB
-----END PGP SIGNATURE-----




      reply	other threads:[~2012-02-09 19:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 20:58 [PATCH][meta-oe 0/3] O.S. Systems' systemd related changes Otavio Salvador
2012-02-07 20:58 ` [PATCH][meta-oe 1/3] Revert "systemd.bbclass: depends on systemd" Otavio Salvador
2012-02-09 16:01   ` Martin Jansa
2012-02-07 20:58 ` [PATCH][meta-oe 2/3] udisks: explicitly depends on systemd Otavio Salvador
2012-02-09 16:01   ` Martin Jansa
2012-02-07 20:58 ` [PATCH][meta-oe 3/3] polkit: " Otavio Salvador
2012-02-09 16:00   ` Martin Jansa
2012-02-09 16:14     ` Otavio Salvador
2012-02-09 18:51       ` Koen Kooi [this message]

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='jh14jj$866$2@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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