General cleanup of makefiles and build process
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#2) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#3) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#4) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#5) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#6) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#7) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#8) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#9) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#11) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/5645 (build: Start using library versioning for various libraries) posted (#12) for review on master by Harshavardhana (harsha)
COMMIT: http://review.gluster.org/5645 committed in master by Vijay Bellur (vbellur) ------ commit c2b09dc87e0763dfdff1e93a1dc6cc4c05f091bf Author: Harshavardhana <harsha> Date: Sat Aug 17 13:01:23 2013 -0700 build: Start using library versioning for various libraries According to libtool three individual numbers stand for CURRENT:REVISION:AGE, or C:R:A for short. The libtool script typically tacks these three numbers onto the end of the name of the .so file it creates. The formula for calculating the file numbers on Linux and Solaris is /path/to/library/<library_name>.(C - A).(A).(R) As you release new versions of your library, you will update the library's C:R:A. Although the rules for changing these version numbers can quickly become confusing, a few simple tips should help keep you on track. The libtool documentation goes into greater depth. In essence, every time you make a change to the library and release it, the C:R:A should change. A new library should start with 0:0:0. Each time you change the public interface (i.e., your installed header files), you should increment the CURRENT number. This is called your interface number. The main use of this interface number is to tag successive revisions of your API. The AGE number is how many consecutive versions of the API the current implementation supports. Thus if the CURRENT library API is the sixth published version of the interface and it is also binary compatible with the fourth and fifth versions (i.e., the last two), the C:R:A might be 6:0:2. When you break binary compatibility, you need to set AGE to 0 and of course increment CURRENT. The REVISION marks a change in the source code of the library that doesn't affect the interface-for example, a minor bug fix. Anytime you increment CURRENT, you should set REVISION back to 0. Change-Id: Id72e74c1642c804fea6f93ec109135c7c16f1810 BUG: 862082 Signed-off-by: Harshavardhana <harsha> Reviewed-on: http://review.gluster.org/5645 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/6790 (build: GFAPI_VERSION should be 6.0.0 not 0.0.6) posted (#1) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/6790 (build: GFAPI_VERSION should be 6.0.0 not 0.0.6) posted (#2) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/6790 (build: GFAPI_VERSION should be 6.0.0 not 0.0.6) posted (#3) for review on master by Harshavardhana (harsha)
COMMIT: http://review.gluster.org/6790 committed in master by Vijay Bellur (vbellur) ------ commit a7243ea310613ad0681fd68bc951492fe311916b Author: Harshavardhana <harsha> Date: Sat Jan 25 02:39:11 2014 -0800 build: GFAPI_VERSION should be 6.0.0 not 0.0.6 -------------------------------------> "In essence, every time you make a change to the library and release it, the C:R:A should change. A new library should start with 0:0:0. Each time you change the public interface (i.e., your installed header files), you should increment the CURRENT number." So the version which was 3 became 5 when discard API was added and became 6 when zerofill was added. As per the above description, API addition will result in a change to the installed header (glfs.h) and hence warrants a change in CURRENT number ? Should you have changed the version to 6.0.0 instead of 0.0.6 ? <------------------------------------ Thanks Bharata B Rao <bharata.rao> for pointing this out Change-Id: I0aa980a6713fbd28922a94c5debb170a89aa3512 BUG: 862082 Signed-off-by: Harshavardhana <harsha> Reviewed-on: http://review.gluster.org/6790 Reviewed-by: Niels de Vos <ndevos> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Bharata B Rao <bharata.rao> Reviewed-by: Vijay Bellur <vbellur>