On Mon, 2011-08-01 at 16:40 +0200, Martin Zibricky wrote: > Giovanni Bajo píše v Po 01. 08. 2011 v 16:18 +0200: > > Either MacPorts always relies on system's libcups (and *all* its > > dependencies, including libiconv), or it does not. If it does ship > > libiconv but not libcups, they have a bug. > > Well, the fact is that macports, fink and homebrew, all do the same: > - rely on system libcups > - have own version of libconv > > Probably the reason is that nobody wants the burden of maintaining > libcups custom builds. >
OK thanks for clarifying. Some questions: 1) Does it work if we package Leopard's libcups and run under Lion? It would help if somebody tried some testing that would really access printing functions. 2) Does it work if remove libiconv and always use the system one (instead of MacPort's one)? -- Giovanni Bajo :: [email protected] Develer S.r.l. :: http://www.develer.com My Blog: http://giovanni.bajo.it Last post: The algorithms behind OTP tokens
smime.p7s
Description: S/MIME cryptographic signature
