public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Add python-systemd in oe-core or meta-oe?
Date: Wed, 13 Jan 2016 16:44:15 -0500	[thread overview]
Message-ID: <5696C52F.3070807@windriver.com> (raw)

https://github.com/systemd/python-systemd

This is a python module that was present in the systemd
v215 source but removed by v223.

So does anyone think it's useful say for testing?
If so, should it be added to oe-core or meta-oe?


 From the github page:

python-systemd

Python module for native access to the systemd facilities. Functionality 
is seperated into a number of modules:

systemd.journal:
supports sending of structured messages to the journal and reading 
journal files,

systemd.daemon:
wraps parts of libsystemd useful for writing daemons and socket activation,

systemd.id128:
provides functions for querying machine and boot identifiers and a lists 
of message identifiers provided by systemd,

systemd.login:
wraps parts of libsystemd used to query logged in users and available 
seats and machines.



It's present in several distros (F23, ubu-14.04):
   http://pkgs.org/search/python-systemd


-- 
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
Canada, K2K 2W5


             reply	other threads:[~2016-01-13 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 21:44 Randy MacLeod [this message]
2016-01-18 12:21 ` Add python-systemd in oe-core or meta-oe? Burton, Ross

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=5696C52F.3070807@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=openembedded-core@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