Re: [Fink-devel] -release to -version-info conversion

[TheSin]

will libtool the only way to control the compat version is version-info, with release there will be no compat version so a good libtool will make 1 and an old unpatched libtool will make it 0...either way it's bad, when the maintainer of a pkg finally update from release to version-info I can almost guarantee he will use (x+y):z:y and thus it'll work perfectly, since this convo I've been checking all the configure scripts of the libs that work, and all the ones that aren't hard coded use this method.

-Justin

On 19-Nov-03, at 3:39 AM, Max Horn wrote:

I think that is a *very* bad idea what you are doing, Justin. It is quite likely to cause us pain in the future. If your only justification is "ugly filenames", then I ask you to stop doing it. It's a hack based on incomplete understanding of the issue, by what I hear from you. You are changing the filenames and the compat version info in the .dylib in a semi-arbitrary fashion. Not good.

smime.p7s
Description: S/MIME cryptographic signature

PGP.sig
Description: This is a digitally signed message part