From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] python-systemd: New package.
Date: Thu, 01 Dec 2016 14:23:58 +0100 [thread overview]
Message-ID: <1480598638.16038.1.camel@ipfire.org> (raw)
In-Reply-To: <1480598247.13949.108.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3047 bytes --]
Hello thanks for reviewing my commit:
I'll send a new patch with the renamed package name.
No it seems, that there is no runtime dependency to a specific systemd
version.
Best regards,
-Stefan
> Hi,
>
> looks good, but the package should be called python3-systemd which
> complies with
> the naming of the other ones.
>
> Isn't there a possible runtime dependency to a specific version of
> systemd
> required?
>
> On Thu, 2016-12-01 at 14:10 +0100, Stefan Schantl wrote:
> >
> > This package now contains the python bindings for systemd.
> >
> > Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> > ---
> > python-systemd/python-systemd.nm | 60
> > ++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 60 insertions(+)
> > create mode 100644 python-systemd/python-systemd.nm
> >
> > diff --git a/python-systemd/python-systemd.nm b/python-
> > systemd/python-
> > systemd.nm
> > new file mode 100644
> > index 0000000..a291874
> > --- /dev/null
> > +++ b/python-systemd/python-systemd.nm
> > @@ -0,0 +1,60 @@
> > +##################################################################
> > ###########
> > ##
> > +# IPFire.org - An Open Source Firewall
> > Solution #
> > +# Copyright (C) - IPFire Development Team <info(a)ipfire.org>
> >
> > #
> > +##################################################################
> > ###########
> > ##
> > +
> > +name = python-systemd
> > +version = 232
> > +release = 1
> > +
> > +groups = Development/Tools
> > +url = https://github.com/systemd/python-systemd
> > +license = LGPLv2+
> > +summary = Python module wrapping systemd functionality.
> > +
> > +description
> > + This package contains various Python modulse for a native
> > access to
> > + the systemd facilities.
> > +end
> > +
> > +source_dl = https://github.com/systemd/python-systemd/archive/v%{
> > version}.ta
> > r.gz#/
> > +
> > +build
> > + requires
> > + python3-devel >= 3.4
> > + systemd-devel
> > + end
> > +
> > + prepare_cmds
> > + sed -i 's/py\.test/pytest/' Makefile
> > + end
> > +
> > + make_build_targets += \
> > + PYTHON=%{python3}
> > +
> > + test
> > + # Disable testsuite, because pytest is required
> > + # which is currently not available.
> > + #make PYTHON=%{python3} check
> > + end
> > +
> > + make_install_targets +=\
> > + PYTHON=%{python3}
>
> There could be a space between += and \
>
> >
> > +
> > + install_cmds
> > + # Remove accidently installed files from
> > testsuite.
> > + rm -rvf
> > %{BUILDROOT}%{python3_sitearch}/systemd/test
> > + end
> > +end
>
> Accidentially?
>
> >
> > +
> > +packages
> > + package %{name}
> > + obsoletes
> > + python3-systemd >= 221
> > + end
> > + end
> > +
> > + package %{name}-debuginfo
> > + template DEBUGINFO
> > + end
> > +end
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-12-01 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 13:10 Stefan Schantl
2016-12-01 13:17 ` Michael Tremer
2016-12-01 13:23 ` Stefan Schantl [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=1480598638.16038.1.camel@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.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