Am Donnerstag, 8. August 2002, 22:20:01 Uhr MET, schrieb Stefan Siegel: > How about adding two packages named "libfakecss" and "libfakecss-devel" > to cooker which contain > > * libfakecss > ========== > - /usr/lib/libcss.so.0.1.0 (the same functions as libcss, but with > empy bodys: all returning (int)0, void > or NULL) > > * libfakecss-devel > ================ > - /usr/include/css.h > - /usr/lib/libcss.so ->/usr/lib/libcss.so.0.1.0 > - /usr/lib/libcss.so.0.1.0 -> /usr/lib/libcss.so.0.1.0 > > You can add "BuildRequire: libfakecss-devel" then which binds against our > dummy libcss. We could even ship this "libfakecss" with the ditribution, as > she does nothing. > > If vendors replace "libfakecss" by a package named "libcss" which provides > some other functionaity it is not our fault. So nobody can sue us. Specially > if we mention it in the information (rpm -qi) as in the docs of libfakecss > that it is illegal in US to replace it by a RPM named libcss ...
Hi, I think this is unneeded, because most applications that need css are based on libdvdread. You just have to install libdvdcss to enable the support for the encrypted DVDs, no recompiling needed at all. -- G�tz Waschk <> master of computer science <> University of Rostock http://wwwstud.informatik.uni-rostock.de/~waschk/waschk.asc for PGP key --> Logout Fascism! <--
