Ok, I will adopt the 1.18.2 naming convention for the next update, and modify the NEWS file as well.
Regarding being more secure... well, this is color management and not a security package, so probably Bob is right and all this effort may be pointless. What do you think? Giving a MD5 message digest would help? Do we need anything else? Regards Marti Quoting Kai-Uwe Behrmann <k...@gmx.de>: > Am 19.04.09, 12:12 -0500 schrieb Bob Friesenhahn: > >> I extracted lcms-1.18a.tar.gz and notice that there are no >> documentation updates and that the package extracts as lcms-1.18 >> rather than lcms-1.18a. The only way to tell that there has been an >> update is that src/cmsxform.c is more recent than the NEWS file. The >> shared library builds with the same versioning information. >> >> This approach causes problems for users since it is difficult to tell >> if their installed 1.18 has the security patch or not. > > It is typical for many projects to use a major.minor.patch, e.g. > 1.18.1, naming scheme for such minimal changes like e.g. security > patches. But well, 1.18.1 sounds more technical otherwise it seeme > very practical. > > > kind regards > Kai-Uwe Behrmann > -- > developing for colour management www.behrmann.name + www.oyranos.org > > ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
