[TRANSLATE] web/xml/packaging packaging.en.xml,1.32,1.33

Modified Files:
	packaging.en.xml 
Log Message:
documenting BuildDependsOnly policy


Index: packaging.en.xml
===================================================================
RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -d -r1.32 -r1.33
--- packaging.en.xml	15 Jun 2004 18:31:38 -0000	1.32
+++ packaging.en.xml	23 Jun 2004 22:22:52 -0000	1.33
@@ -737,7 +737,49 @@
 This ensures that the versions match, and also guarantees that barN
 automatically "inherits" all the dependencies of barN-shlibs.
 </p>
-<p><em>The Shlibs field:</em>
+<p><em>The BuildDependsOnly field</em>
+</p><p>
+When libraries are being upgraded over time, it is often necessary to have
+two versions of the header files available during a transition period,
+with one version used for compiling some things and the other version
+used for compiling others.  For this reason, the packages containing
+header files must be constructed with some care.  If both foo-dev and
+bar-dev contain overlapping headers, then foo-dev should declare
+</p>
+<codeblock>
+  Conflicts: bar-dev
+  Replaces: bar-dev
+</codeblock>
+<p>and similarly bar-dev declares Conflicts/Replaces on foo-dev.
+</p><p>
+In addition, both packages should declare
+</p>
+<codeblock>
+  BuildDependsOnly: True
+</codeblock>
+<p>This inhibits others from writing packages which depend on foo-dev or
+bar-dev, since any such dependency will prevent the smooth operation of the
+Conflicts/Replaces method.
+</p><p>
+There are some packages containing header files for which it's not
+appropriate to declare BuildDependsOnly to be true.  In that case,
+the package should declare
+</p>
+<codeblock>
+  BuildDependsOnly: False
+</codeblock>
+<p>and the reason must be given in the DescPackaging field.
+</p><p>
+The BuildDependsOnly field should only be mentioned in the package's .info
+file if the package contains header files, installed into /sw/include.
+</p><p>
+As of fink 0.20.5, "fink validate" will issue a warning for any .deb
+which contains header files and at least one dylib, and does not declare
+BuildDependsOnly to be either true or false.  (It is possible that in
+future versions of fink, this warning will be expanded to cover the case of
+a .deb with header files and a static library as well.)
+</p>
+<p><em>The Shlibs field</em>
 </p><p>
 In addition to putting the shared libraries in the correct package, as of
 version 4 of this policy, you must also declare all of the shared libraries
@@ -1562,9 +1604,11 @@
 A boolean value which indicates that no other packages should Depend on
 this one, they should only BuildDepend.
 </p>
-<p>As of fink 0.20.3, the value of this field is recorded into the .deb
-file when a package is built.  Therefore, <em>if you change the value of
-BuildDependsOnly you must increase the revision number</em> of the package.
+<p>As of fink 0.20.5, the presence or absence of this field, and its value
+if present, are recorded into the .deb
+file when the package is built.  Therefore, <em>if you change the value of
+BuildDependsOnly or if you add or remove it,
+you must increase the revision number</em> of the package.
 </p>
 </itemd></item>
 



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Fink-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-commits



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com