2014.11.19 23:59 "Re: [Tiff] libtiff release pending?", by Bob Friesenhahn

The shared library minor revision should always change whenever a new tarball is released.

ok, so libtiff-4.0.4RC1.tar.gz and libtiff-4.0.4.tar.gz wouldn't be binary identical?

They may be binary identical but it is not expected behavior for a library delivered from one package to overwrite the library delivered by a different package. It is polite to not overwrite. For example, the libraries might be built with somewhat different build options, or an operating system package manager might expect to uninstall the older version.

Otherwise the library from the new package would overwrite the built library from the previous package.

Which would be fine for 4.0.4RC2 with respect to 4.0.4RC1, wouldn't it?

I am not sure. We have no control over what people choose to do with release candidates. They may produce an installable release package from it. We should assume that any tarball produced may be used to produce packages used to install the software.

It seems ok for the versioning used by applications to be updated to the expected final versions.

Not sure to understand what you mean here. Examples?

I mean the content of libtiff header files or constant strings returned by the library to applications to identify the version of the library.

Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/