> Alexander Strange has submitted a revised version of the gimp package to > the tracker, taking over as maintainer from chrisp. (Thanks!) Thanks! We need more packages!
> There is one issue with this package that I wanted to bring up. It has > a linker flag -lcrypto and so will either use /usr/lib/libcrypto.dylib > or /sw/lib/libcrypto.dylib, depending on whether the fink openssl > package > is installed or not. Hmmm. > My reaction to this is that there will need to be two packages: > Package gimp (in the main tree): > Conflicts: openssl > Package gimp-ssl (in the crypto tree): > Depends: openss I'd almost recommend that the names be gimp and gimp-libcrypo or gimp and gimp-crypto since it is really not using the secure socket layer, only the crypto functions. > Otherwise, we might get binary-incompatible versions... and we can't > simply require "Depends: openssl" because that will force gimp into > the crypto tree. We might need to figure out how to get gimp to compile without /usr/lib/libcrypto.dylib for the package 'gimp' > Any other thoughts or opinions about this? > > -- Dave Kyle Moffett _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
