Justin, that section of the fink docs was added 10 months ago by dmalloc.
I don't remember what discussion might have preceded that, but I certainly
strongly disagree with the implication which is made there. We definitely
should not be changing the versioning that is being used by the upstream
ma
OH i agree there, just saying if this is the official stand on this we
should take that down, I on the other will continue as I have. It's
much nicer and easy to manage, and I don't have to make a pkgxyz
release for every upstream release when they don't break compat.
-TS
On 19-Nov-03, at 3
TheSin wrote:
further more, on the fink site!
http://fink.sourceforge.net/doc/porting/libtool.php#dylibversionfix
Can you point me at the libtool docs/code which say -release is
deprecated please?
Just because it is on the fink web site doesn't necessarily mean it is
correct :-p
Peter
further more, on the fink site!
http://fink.sourceforge.net/doc/porting/libtool.php#dylibversionfix
-TS
On 19-Nov-03, at 7:52 AM, Peter O'Gorman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
TheSin wrote:
| will libtool the only way to control the compat version is
version-info,
| wit
it's ugly because of how you need to use them after plus everyone I've
changed to date has changed upstream in the next release. And -release
is obsolete and should not be used in all the docs I've read about it.
It's old and should be changed to something else. Anyhow...I thought
I'd just l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
TheSin wrote:
| 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 maintai
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 a
Am Mittwoch, 19.11.03 um 05:32 Uhr schrieb TheSin:
but it'll link libfoo.1.2.1.dylib so the filename has the right
version, I'm not sure about the compat versions, but it should work as
it'll never go backwards.
I never heard of --version-number...I'll research it, but my little
(x+y):z:y work
but it'll link libfoo.1.2.1.dylib so the filename has the right
version, I'm not sure about the compat versions, but it should work as
it'll never go backwards.
I never heard of --version-number...I'll research it, but my little
(x+y):z:y works better then -release for now, all of gnome 2.4, gn
Benjamin Reed wrote:
My mistake, I talked to Peter; -release *is* bad. However, my point
stands, you're supposed to switch it to "-version-number" (number, as
opposed to info) instead, if possible; it depends on what version of
libtool you have whether it's available or not.
-version-number wa
TheSin wrote:
just cause i want to doc it someplace I've found that in almost
everycase this is how you can convert -release to -version-info
in other words ugly (libfoo-0.0.0.dylib, libfoo-0.0.0.0.dylib and
libfoo-0.0.0.0.0.0.dylib)
to nice (libfoo.dylib, libfoo.0.dylib and libfoo.0.0.0.dylib)
-release is bad news on OSX, IIRC it's very old on all systems and
should be phased out. There should be any libs on darwin with
libfoo-0.0.0 they should always be libfoo.0.0.0 which means replacing
-release with -version-info. The problem is always getting the value
for version-info as it ca
TheSin wrote:
just cause i want to doc it someplace I've found that in almost
everycase this is how you can convert -release to -version-info
in other words ugly (libfoo-0.0.0.dylib, libfoo-0.0.0.0.dylib and
libfoo-0.0.0.0.0.0.dylib)
to nice (libfoo.dylib, libfoo.0.dylib and libfoo.0.0.0.dylib)
just cause i want to doc it someplace I've found that in almost
everycase this is how you can convert -release to -version-info
in other words ugly (libfoo-0.0.0.dylib, libfoo-0.0.0.0.dylib and
libfoo-0.0.0.0.0.0.dylib)
to nice (libfoo.dylib, libfoo.0.dylib and libfoo.0.0.0.dylib)
if you see -r
14 matches
Mail list logo
