I'd like to make some remarks on the 9.0 lib policy thing as stated in the changelog
>--=-=-= > >* Thu May 16 2002 Yves Duret <[EMAIL PROTECTED]> 6b-23mdk > >- 9.0 lib policy: added libjpeg62-static-devel > This is all very nice, moving 3 or so files into (yet) another package: /usr/lib/libgif.a /usr/lib/libungif.a /usr/lib/libungif.la /usr/share/doc/libungif4-static-devel-4.1.0 The consequence is that this breaks the BuildRequires of a number of packages. I'm wondering if it's worth it to make so many sub-packages... See: http://eijk.homelinux.org/build/cooker/i586/problem/Epplets-0.5-8mdk.src.rpm.txt /bin/sh ../libtool --mode=link gcc -O3 -fomit-frame-pointer -pipe -mcpu=pentiumpro -march=i586 -ffast-math -fno-strength-reduce -I/usr/X11R6/include -o libepplet.la -rpath /usr/lib -version-info 1:0:1 epplet.lo snprintf.lo -L/usr/lib -lImlib -ljpeg -ltiff -ljpeg -lz -lungif -lpng -lz -lm -lXext -L/usr/X11R6/lib -lSM -lICE -lXext -lX11 grep: /usr/lib/libjpeg.la: No such file or directory sed: can't read /usr/lib/libjpeg.la: No such file or directory libtool: link: `/usr/lib/libjpeg.la' is not a valid libtool archive make[2]: *** [libepplet.la] Error 1 make[2]: Leaving directory `/home/cooker/RPM/BUILD/Epplets-0.5/api' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/cooker/RPM/BUILD/Epplets-0.5' make: *** [all-recursive-am] Error 2 error: Bad exit status from /home/cooker/tmp/rpm-tmp.94123 (%build) I'm wondering who is going to fix the breakage of this change... A number of BuildRequires will need to be revisited, and judging from previous experiences, it ain't gonna happen :-/ In this case I've only found 2 packages that need to be revisited: Epplets-0.5-8mdk.src.rpm libfnlib0-0.5-2mdk.src.rpm But if more packages are converted to this new policy then the list will grow... Perhaps I don't see the benefits of this policy, maybe somebody can enlighten me? with kind regards. Stefan
