diff options
3 files changed, 33 insertions, 12 deletions
diff --git a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml index 084c8f7c50..b254ccd18b 100644 --- a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.11 1999/09/06 06:53:02 peter Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.12 1999/11/07 01:54:52 chris Exp $ --> <chapter id="policies"> @@ -331,7 +331,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> <listitem> <para>If there is a change that is backwards compatible, bump minor - number</para> + number (note that ELF systems ignore the minor number)</para> </listitem> <listitem> @@ -344,7 +344,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> call syntax etc. will force the major version number to change.</para> <para>Stick to version numbers of the form major.minor - (<replaceable>x</replaceable>.<replaceable>y</replaceable>). Our + (<replaceable>x</replaceable>.<replaceable>y</replaceable>). Our a.out dynamic linker does not handle version numbers of the form <replaceable>x</replaceable>.<replaceable>y</replaceable>.<replaceable>z</replaceable> well. Any version number after the <replaceable>y</replaceable> @@ -366,9 +366,16 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> <filename>libc.so.2.0</filename>, even if the program was initially linked with <filename>libc.so.2.0</filename>.</para> </note> + + <para>In addition, our ELF dynamic linker does not handle minor version + numbers at all. However, one should still specify a major and minor + version number as our <filename>Makefile</filename>s "do the right thing" + based on the type of system. <para>For non-port libraries, it is also our policy to change the shared - library version number only once between releases. When you make a + library version number only once between releases. In addition, it is + our policy to change the major shared library version number only once + between major OS releases. Ie: X.0 to (X+1).0. When you make a change to a system library that requires the version number to be bumped, check the <filename>Makefile</filename>'s commit logs. It is the responsibility of the committer to ensure that the first such change diff --git a/en_US.ISO8859-1/books/handbook/policies/chapter.sgml b/en_US.ISO8859-1/books/handbook/policies/chapter.sgml index 084c8f7c50..b254ccd18b 100644 --- a/en_US.ISO8859-1/books/handbook/policies/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/policies/chapter.sgml @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.11 1999/09/06 06:53:02 peter Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.12 1999/11/07 01:54:52 chris Exp $ --> <chapter id="policies"> @@ -331,7 +331,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> <listitem> <para>If there is a change that is backwards compatible, bump minor - number</para> + number (note that ELF systems ignore the minor number)</para> </listitem> <listitem> @@ -344,7 +344,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> call syntax etc. will force the major version number to change.</para> <para>Stick to version numbers of the form major.minor - (<replaceable>x</replaceable>.<replaceable>y</replaceable>). Our + (<replaceable>x</replaceable>.<replaceable>y</replaceable>). Our a.out dynamic linker does not handle version numbers of the form <replaceable>x</replaceable>.<replaceable>y</replaceable>.<replaceable>z</replaceable> well. Any version number after the <replaceable>y</replaceable> @@ -366,9 +366,16 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> <filename>libc.so.2.0</filename>, even if the program was initially linked with <filename>libc.so.2.0</filename>.</para> </note> + + <para>In addition, our ELF dynamic linker does not handle minor version + numbers at all. However, one should still specify a major and minor + version number as our <filename>Makefile</filename>s "do the right thing" + based on the type of system. <para>For non-port libraries, it is also our policy to change the shared - library version number only once between releases. When you make a + library version number only once between releases. In addition, it is + our policy to change the major shared library version number only once + between major OS releases. Ie: X.0 to (X+1).0. When you make a change to a system library that requires the version number to be bumped, check the <filename>Makefile</filename>'s commit logs. It is the responsibility of the committer to ensure that the first such change diff --git a/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml b/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml index 084c8f7c50..b254ccd18b 100644 --- a/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.11 1999/09/06 06:53:02 peter Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.12 1999/11/07 01:54:52 chris Exp $ --> <chapter id="policies"> @@ -331,7 +331,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> <listitem> <para>If there is a change that is backwards compatible, bump minor - number</para> + number (note that ELF systems ignore the minor number)</para> </listitem> <listitem> @@ -344,7 +344,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> call syntax etc. will force the major version number to change.</para> <para>Stick to version numbers of the form major.minor - (<replaceable>x</replaceable>.<replaceable>y</replaceable>). Our + (<replaceable>x</replaceable>.<replaceable>y</replaceable>). Our a.out dynamic linker does not handle version numbers of the form <replaceable>x</replaceable>.<replaceable>y</replaceable>.<replaceable>z</replaceable> well. Any version number after the <replaceable>y</replaceable> @@ -366,9 +366,16 @@ obrien@FreeBSD.org - 30 March 1997</programlisting> <filename>libc.so.2.0</filename>, even if the program was initially linked with <filename>libc.so.2.0</filename>.</para> </note> + + <para>In addition, our ELF dynamic linker does not handle minor version + numbers at all. However, one should still specify a major and minor + version number as our <filename>Makefile</filename>s "do the right thing" + based on the type of system. <para>For non-port libraries, it is also our policy to change the shared - library version number only once between releases. When you make a + library version number only once between releases. In addition, it is + our policy to change the major shared library version number only once + between major OS releases. Ie: X.0 to (X+1).0. When you make a change to a system library that requires the version number to be bumped, check the <filename>Makefile</filename>'s commit logs. It is the responsibility of the committer to ensure that the first such change |