From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] systemd: split out systemd-analyze
Date: Tue, 10 Jan 2012 08:27:01 +0100 [thread overview]
Message-ID: <jegp84$91t$1@dough.gmane.org> (raw)
In-Reply-To: <20120109133703.GA5503@ad.chargestorm.se>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 09-01-12 14:37, Anders Darander schreef:
> * Martin Jansa <martin.jansa@gmail.com> [120109 14:28]:
>
>> On Mon, Jan 09, 2012 at 02:18:38PM +0100, Anders Darander wrote:
>>> Split systemd-analyze to a separate package, to remove the implicit
>>> dependency on python. (At least the rpm-packaging backend created a
>>> run-time dependency on python).
>
>>> +PACKAGES =+ "${PN}-gui ${PN}-vconsole-setup ${PN}-initramfs
>>> ${PN}-analyze"
>
>>> USERADD_PACKAGES = "${PN}" GROUPADD_PARAM_${PN} = "-r lock"
>
>>> +FILES_${PN}-analyze = "${bindir}/systemd-analyze"
>
>> according to your commit message, why not add RDEPENDS_${PN}-analyze =
>> "python" here?
>
> Yes, I should probably spin a v2 with: RDEPENDS_${PN}-analyze =
> "python-dbus" as python alone isn't enough to run systemd-analyze.
Don't forget python-pycairo for 'systemd-analyze plot'
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAk8L6EMACgkQMkyGM64RGpFsMwCfYYRYu/3dMHcSatOubVTWgz8U
i8kAoI8iJsmGCdwTYWz492C5LJMn3uPH
=BrPL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-01-10 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 13:16 [PATCH 0/2] systemd: SRC_URI fix + package split Anders Darander
2012-01-09 13:18 ` [PATCH 1/2] systemd: git repo moved Anders Darander
2012-01-09 13:18 ` [PATCH 2/2] systemd: split out systemd-analyze Anders Darander
2012-01-09 13:28 ` Martin Jansa
2012-01-09 13:37 ` Anders Darander
2012-01-09 13:44 ` Anders Darander
2012-01-09 14:34 ` Otavio Salvador
2012-01-10 7:27 ` Koen Kooi [this message]
2012-01-10 7:53 ` Anders Darander
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='jegp84$91t$1@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 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.