Translate: [cvs] web/xml/packaging packaging.en.xml, 1.90, 1.91

Begin forwarded message:

> From: "David R. Morrison" <[email protected]>
> Date: December 3, 2006 1:21:26 PM PST
> To: [email protected]
> Subject: [cvs] web/xml/packaging packaging.en.xml,1.90,1.91
> Reply-To: [email protected]
>
> Update of /cvsroot/fink/web/xml/packaging
> In directory sc8-pr-cvs5.sourceforge.net:/tmp/cvs-serv9877
>
> Modified Files:
> 	packaging.en.xml
> Log Message:
> Modify the Shlibs field to handle the case of 64bit libraries.
>
>
> Index: packaging.en.xml
> ===================================================================
> RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
> retrieving revision 1.90
> retrieving revision 1.91
> diff -u -d -r1.90 -r1.91
> --- packaging.en.xml	29 Nov 2006 19:45:40 -0000	1.90
> +++ packaging.en.xml	3 Dec 2006 21:21:22 -0000	1.91
> @@ -565,14 +565,16 @@
>  <p>
>  Fink has a new policy about shared libraries, effective in  
> February 2002.
>  This section of the documentation discusses version 4
> -of the policy, which coincides with the release of Fink's 0.5.0  
> distribution.
> +of the policy, which coincides with the release of Fink's 0.5.0  
> distribution
> +(as well as some updates from December, 2006 to handle 64bit  
> libraries).
>  We begin with a quick summary, and then discuss things in more  
> detail.
>  </p><p>
>  Any package which builds shared libraries and is either (1) being  
> put into
>    the stable tree, or (2) a new package in Fink, should treat its  
> shared
>    libraries according to Fink's policy.  This means:</p>
>  <ul>
> -<li>   verify, using <code>otool -L</code>, that
> +<li>   verify, using <code>otool -L</code> (or <code>otool64 -L</ 
> code> for
> +64bit libraries), that
>         the install_name of each library and
>         its compatibility and current version numbers are correct </ 
> li>
>  <li>   put the shared libraries in a separate package (except for the
> @@ -700,7 +702,8 @@
>  When building shared libraries under major version N, it is  
> important that
>  the "install_name" of the library be <filename>%p/lib/bar.N.dylib</ 
> filename>.
>  (You can
> -find the install_name by running <code>otool -L</code> on your  
> library.)  The
> +find the install_name by running <code>otool -L</code> on your  
> library,
> +or <code>otool64 -L</code> for 64bit libraries.)  The
>  actual library file should be installed at
>  </p>
>  <codeblock>
> @@ -725,7 +728,7 @@
>  check that they have been done correctly in your case.  You should  
> also
>  check that current_version and compatibility_version were defined
>  appropriately for your shared libraries.  (These are also shown  
> with the
> -<code>otool -L</code> query.)
> +<code>otool -L</code> query, or <code>otool64 -L</code> for 64bit  
> libraries.)
>  </p><p>
>  Files are then divided between the two packages as follows
>  </p>
> @@ -832,9 +835,12 @@
>  version 4 of this policy, you must also declare all of the shared  
> libraries
>  using the <code>Shlibs</code> field.  This field has one line for  
> each
>  shared library, which contains the <code>-install_name</code> of the
> -library, the <code>-compatibility_version</code>, and versioned
> +library, the <code>-compatibility_version</code>, versioned
>  dependency information specifying the Fink package which provides
> -this library at this compatibility version.  The dependency should
> +this library at this compatibility version, and the library
> +architecture.  (The library architecture may either be "32", "64", or
> +"32-64", and may be absent; the value defaults to "32" if it is  
> absent.)
> +The dependency should
>  be stated in the form <code> foo (>= version-revision)</code> where
>  <code>version-revision</code> refers to
>  the <em>first</em> version of a Fink package which made
> @@ -842,14 +848,16 @@
>  a declaration</p>
>  <codeblock>
>    Shlibs: &lt;&lt;
> -    %p/lib/bar.1.dylib 2.1.0 bar1 (>= 1.1-2)
> +    %p/lib/bar.1.dylib 2.1.0 bar1 (>= 1.1-2) 32
>    &lt;&lt;
>  </codeblock>
> -<p>indicates that a library with <code>-install_name</code> %p/lib/ 
> bar.1.dylib
> +<p>indicates that a (32bit)
> +library with <code>-install_name</code> %p/lib/bar.1.dylib
>  and <code>-compatibility_version</code> 2.1.0 has been installed  
> since
>  version 1.1-2 of the <em>bar1</em> package.  In addition, this  
> declaration
>  amounts to  a promise
> -from the maintainer that a library with this name and a  
> compatibility-version
> +from the maintainer that a 32bit
> +library with this name and a compatibility-version
>  of at least 2.1.0 will always be found in later versions of the  
> <em>bar1</em>
>  package.
>  </p><p>
> @@ -2757,11 +2765,14 @@
>  <em>Introduced in fink 0.11.0.</em>
>  This field declares the shared libraries which are installed in the
>  package.  There is one line for each
> -shared library, which contains three items separated by whitespace:
> +shared library, which contains three or four items separated by  
> whitespace:
>  the <code>-install_name</code> of the
> -library, the <code>-compatibility_version</code>, and versioned
> +library, the <code>-compatibility_version</code>, versioned
>  dependency information specifying the Fink package which provides
> -this library at this compatibility version.  The dependency should
> +this library at this compatibility version, and the
> +library architecture.  (The library architecture may either be  
> "32", "64", or
> +"32-64", and may be absent; the value defaults to "32" if it is  
> absent.)
> +The dependency should
>  be stated in the form <code> foo (>= version-revision)</code> where
>  <code>version-revision</code> refers to
>  the <em>first</em> version of a Fink package which made
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Fink-commits mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fink-commits

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
fink-i18n mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-i18n