Re: [HACKERS] Shared library versions
On Wed, 9 May 2001, Peter Eisentraut wrote: We did not bump the shared library versions before the 7.1 release. Maybe we should do this before 7.1.2 goes out. Ummm ... unless there are any changes that would require someone to recompile their apps between v7.1.1 and v7.1.2, I don't think so ... they we are just creating potential problems for those upgrading from v7.1/v7.1.1 to the latest stable, where there are no changes ... If we were to do it, it would have to be on the v7.x, not v7.x.y ... ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Shared library versions
Bruce Momjian [EMAIL PROTECTED] writes: We did not bump the shared library versions before the 7.1 release. Maybe we should do this before 7.1.2 goes out. I thought I did that long ago for 7.1, or I should have anyway. I don't see the commits either. Seems we can't do it in a minor release. I agree, too late now. Isn't there a checklist someplace of things to do while preparing a release? Check shared library version numbers should be on it... regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Shared library versions
On Wed, 9 May 2001, Bruce Momjian wrote: We did not bump the shared library versions before the 7.1 release. Maybe we should do this before 7.1.2 goes out. I thought I did that long ago for 7.1, or I should have anyway. I don't see the commits either. Seems we can't do it in a minor release. Will have to wait for 7.2, but since there really wasn't much API change in 7.1, I think we are OK. Not sure if we should update them if there are no API changes, or were there? IMHO, it should only be changed if there are incompatibilities between releases ... we modify the API, mainly ... anything more then that, and we're making ppl recompile to pull in libraries that only unlying code has changed, but not the API ... ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Shared library versions
Peter Eisentraut [EMAIL PROTECTED] writes: The Hermit Hacker writes: IMHO, it should only be changed if there are incompatibilities between releases ... we modify the API, mainly ... anything more then that, and we're making ppl recompile to pull in libraries that only unlying code has changed, but not the API ... ISTM that you should read up on shared library versioning. I second that... if new functionality is added, bump the minor. If functionality changes or is removed, bump the major. -- Trond Eivind Glomsrød Red Hat, Inc. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Shared library versions
On Wed, 9 May 2001, Peter Eisentraut wrote: I'm talking about the minor number. The only thing that effects is that executables would pick up the new version if they have the old one in the path as well, no potential problems. Okay, but, what does that buy you? One overwrites the old library, the other creates one that will over-ride the old library ... either way, you are using the new library, no? ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
