-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 8 Mar 2008, Clemens Kirchgatterer wrote:
Ville Skyttä <ville.skytta@xxxxxx> wrote:
FWIW, I think providing a pkgconfig file is very much a "root"
solution (ditto $foo-config scripts, but *.pc are much simpler to
write and read and have a unified interface). Lots of library
packages (and also some others) provide them nowadays which is great,
and has made the things you express dissatisfaction with in the above
as well as other similar ones pretty much moot.
i can't agree more.
In fact, I think VDR should also provide a *.pc file. I ship one in
Fedora's VDR packages, and a good deal of it would be applicable to
upstream VDR too. Just let me know if you're interested and I'll have
a look at making a upstreamable version of it.
i would even say VDR is broken in the way it handles plaugins. VDR's
Makefile should install all exported vdr headers in
$(PREFIX)/include/vdr and provide a vdr.pc file (as you suggest). then
plugins could be buildable outside of VDR's source directory and
install themself in $(PREFIX)/lib/vdr. as any other plugin capable
program out there i know.
just my 2 cents ...
clemens
Clemens,
you are so damn right!
+1 from my side
Joerg
- --
The beginning is the most important part of the work.
-Plato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFH0nFxSPOsGF+KA+MRArb3AKCG5dH73MNsSs53yspji2hV/v8zDwCgte11
CpaEgzbmHUsy7THwZgUQpa4=
=lClI
-----END PGP SIGNATURE-----
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
