Author Login
Post Reply
2010/3/11 Per Øyvind Karlsen <peroyvind@(protected)>:
> 2. separate uClibc-zlib1, modify rpm build scripts to generate different
> provides/requires for uClibc-linked stuff and also to avoid that any other
> package could've been satisfied by the uClibc-zlib1 package as they
> both would've provided zlib.so.1.
This one might not be such a bad option after all btw., while it seemed a bit
overkill for just one library package, there are some other uClibc
linked library
packages in contrib (they seem kinda abandoned though).
All packages linked against uCllibc (using the uclibc-gcc wrapper) and friends,
does so with full paths, so identifying the provides/requires shouldn't be very
hard to do for rpm scripts.
WDYT?
I'm not opposed to doing it if requested. :)
--
Regards,
Per Øyvind