On Wed, Sep 24, 2014 at 4:58 PM, Jan Engelhardt <jengelh(a)inai.de> wrote:
On Wednesday 2014-09-24 20:38, Greg Freemyer wrote:
I'm trying to package yara with sub-projects of libyara3 and python-yara.
libyara3 as a dependency doesn't make sense because it is a
sub-package of the same package (yara).
If the just-built python interface requires a just-built libyara, then,
both ought to be produced in one go, from one specfile (and thus,
one build invocation).
Like... sssd.spec. This also produces a bunch of shared libs and
some python interfaces.
(One option is to just create an entire second
that only addresses the python binding, then have that BuildRequire
Such is only necessary in the bootstrap phase/when requirements shoot
through the roof (like with util-linux-systemd).
That makes sense conceptually, but what;s the best way to fix it.
How's this prep section? It allows the python setup.py to find the
library after "make" creates it, but before it is installed:
sed -i "/libraries=\['yara'\],/a
That sed line is very dependent on "/libraries=\['yara'\]," being an
existing line in setup.py, but a patch would be equally dependant.
I think I have enough macros in the line I'm adding that it will work
for a reasonable period of time going forward. A patch would not let
me use macros as far as I know.
For clarity of what the sed statement is doing, this is the same thing
in a patch with no macros:
@@ -24,5 +24,6 @@ setup(name='yara-python',
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org