On Tuesday 11 August 2009 10:02:23 Steven Moix wrote:
Hello all,
I'm facing a problem with one of my SPEC files...I'm packaging a program
(motion, in RPM Fusion) that has a startup script. In the start()
section of this startup script, I have added an
"LD_PRELOAD=/usr/lib64/libv4l/v4l2convert.so daemon $motion" to support
more cameras.
You can patch your package to use libv4l directly. Usually it's easy - there
are some issues but... Check some packages using v4l to check what you have to
do to port it.
Also check this blogpost by Hans de Goede (libv4l author) [1].
[1]
http://hansdegoede.livejournal.com/3636.html
Jaroslav
So I naturally added a "Requires: libv4l" in my SPEC file,
but of course
rpmlint complains with "E: explicit-lib-dependency libv4l".
The problem here is that I can't see how RPM could automatically add
libv4l as a dependency when I build the package...it's not in the code,
only a call in the startup script. So...
* Should I consider that libv4l is installed by default on F10/11 and
not put the require.
* Put the require and let rpmlint complain.
Any advice on that?
Note that if you launch the startup script on a system that doesn't have
libv4l, it simply doesn't do the LD_PRELOAD, but still works "as usual".
Thanks
Steven
--
Jaroslav Řezník <jreznik(a)redhat.com>
Associate Software Engineer - Base Operating Systems Brno
Office: +420 532 294 275
Mobile: +420 731 455 332
Red Hat, Inc.
http://cz.redhat.com/