diff options
| -rw-r--r-- | doc/pkgsrc.html | 61 | ||||
| -rw-r--r-- | doc/pkgsrc.txt | 31 |
2 files changed, 68 insertions, 24 deletions
diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index af0766a2077..7868f08bc77 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -225,7 +225,8 @@ builds)</a></span></dt> <dt><span class="sect1"><a href="#manpage-compression">13.5. Man page compression</a></span></dt> <dt><span class="sect1"><a href="#using-PLIST_SRC">13.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt> <dt><span class="sect1"><a href="#platform-specific-plist">13.7. Platform-specific and differing PLISTs</a></span></dt> -<dt><span class="sect1"><a href="#faq.common-dirs">13.8. Sharing directories between packages</a></span></dt> +<dt><span class="sect1"><a href="#build-plist">13.8. Build-specific PLISTs</a></span></dt> +<dt><span class="sect1"><a href="#faq.common-dirs">13.9. Sharing directories between packages</a></span></dt> </dl></dd> <dt><span class="chapter"><a href="#buildlink">14. Buildlink methodology</a></span></dt> <dd><dl> @@ -3356,7 +3357,8 @@ anymore, you can remove that file and run <span class="command"><strong>cvs -q u <dt><span class="sect1"><a href="#manpage-compression">13.5. Man page compression</a></span></dt> <dt><span class="sect1"><a href="#using-PLIST_SRC">13.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt> <dt><span class="sect1"><a href="#platform-specific-plist">13.7. Platform-specific and differing PLISTs</a></span></dt> -<dt><span class="sect1"><a href="#faq.common-dirs">13.8. Sharing directories between packages</a></span></dt> +<dt><span class="sect1"><a href="#build-plist">13.8. Build-specific PLISTs</a></span></dt> +<dt><span class="sect1"><a href="#faq.common-dirs">13.9. Sharing directories between packages</a></span></dt> </dl></dd> <dt><span class="chapter"><a href="#buildlink">14. Buildlink methodology</a></span></dt> <dd><dl> @@ -4873,7 +4875,8 @@ VAR:= ${VAR:N${_othervar_:C/-//}} <dt><span class="sect1"><a href="#manpage-compression">13.5. Man page compression</a></span></dt> <dt><span class="sect1"><a href="#using-PLIST_SRC">13.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt> <dt><span class="sect1"><a href="#platform-specific-plist">13.7. Platform-specific and differing PLISTs</a></span></dt> -<dt><span class="sect1"><a href="#faq.common-dirs">13.8. Sharing directories between packages</a></span></dt> +<dt><span class="sect1"><a href="#build-plist">13.8. Build-specific PLISTs</a></span></dt> +<dt><span class="sect1"><a href="#faq.common-dirs">13.9. Sharing directories between packages</a></span></dt> </dl> </div> <p>The <code class="filename">PLIST</code> file contains a package's @@ -4906,7 +4909,7 @@ VAR:= ${VAR:N${_othervar_:C/-//}} <a name="print-PLIST"></a>13.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span> </h2></div></div></div> <p>If you have used any of the *-dirs packages, as explained in - <a class="xref" href="#faq.common-dirs" title="13.8. Sharing directories between packages">Section 13.8, “Sharing directories between packages”</a>, you may have noticed that + <a class="xref" href="#faq.common-dirs" title="13.9. Sharing directories between packages">Section 13.9, “Sharing directories between packages”</a>, you may have noticed that <span class="command"><strong>make print-PLIST</strong></span> outputs a set of <code class="varname">@comment</code>s instead of real <code class="varname">@dirrm</code> lines. You can also do this for @@ -5052,7 +5055,25 @@ ${PLIST.foo}@dirrm share/bar </div> <div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="faq.common-dirs"></a>13.8. Sharing directories between packages</h2></div></div></div> +<a name="build-plist"></a>13.8. Build-specific PLISTs</h2></div></div></div> +<p>Some packages decide to generate hard-to-guess file names + during installation that are hard to wire down.</p> +<p>In such cases, you can set the + <code class="varname">GENERATE_PLIST</code> variable to shell code + terminated (with a semicolon) that will output PLIST entries which + will be appended to the PLIST</p> +<p>You can find one example in editors/xemacs:</p> +<pre class="programlisting"> + GENERATE_PLIST+= ${ECHO} bin/${DISTNAME}-`${WRKSRC}/src/xemacs -sd`.dmp ; + </pre> +<p>which will append something like + <code class="filename">bin/xemacs-21.4.23-54e8ea71.dmp</code> to the + <code class="filename">PLIST</code>. + </p> +</div> +<div class="sect1"> +<div class="titlepage"><div><div><h2 class="title" style="clear: both"> +<a name="faq.common-dirs"></a>13.9. Sharing directories between packages</h2></div></div></div> <p>A <span class="quote">“<span class="quote">shared directory</span>”</span> is a directory where multiple (and unrelated) packages install files. These directories were problematic because you had to add special @@ -5070,6 +5091,8 @@ ${PLIST.foo}@dirrm share/bar @pkgdir path/to/empty/directory </pre> <p> + or take a look at <code class="varname">MAKE_DIRS</code> and + <code class="varname">OWN_DIRS</code>. </p> </div> </div> @@ -7336,7 +7359,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="tools.questions"></a>18.4. Questions regarding the tools</h2></div></div></div> <div class="qandaset"> -<a name="idm75787664"></a><dl> +<a name="idm77724944"></a><dl> <dt>18.4.1. <a href="#tools.new">How do I add a new tool?</a> </dt> <dt>18.4.2. <a href="#tools.listall">How do I get a list of all available @@ -7355,7 +7378,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <tbody> <tr class="question"> <td align="left" valign="top"> -<a name="tools.new"></a><a name="idm75787280"></a><p><b>18.4.1.</b></p> +<a name="tools.new"></a><a name="idm77724560"></a><p><b>18.4.1.</b></p> </td> <td align="left" valign="top"><p>How do I add a new tool?</p></td> </tr> @@ -7365,7 +7388,7 @@ TOOLS_PLATFORM.true?= true # shell builtin </tr> <tr class="question"> <td align="left" valign="top"> -<a name="tools.listall"></a><a name="idm75786256"></a><p><b>18.4.2.</b></p> +<a name="tools.listall"></a><a name="idm77723536"></a><p><b>18.4.2.</b></p> </td> <td align="left" valign="top"><p>How do I get a list of all available tools?</p></td> @@ -7376,7 +7399,7 @@ TOOLS_PLATFORM.true?= true # shell builtin </tr> <tr class="question"> <td align="left" valign="top"> -<a name="tools.used"></a><a name="idm75785104"></a><p><b>18.4.3.</b></p> +<a name="tools.used"></a><a name="idm77722512"></a><p><b>18.4.3.</b></p> </td> <td align="left" valign="top"><p>How can I get a list of all the tools that a package is using while being built? I want to know whether it @@ -9471,7 +9494,7 @@ place.</p></li> and if you still don't have the answer, ask on the <code class="literal">pkgsrc-users</code> mailing list.</p> <div class="qandaset"> -<a name="idm77324944"></a><dl> +<a name="idm77173392"></a><dl> <dt>22.1. <a href="#devfaq.makeflags">What is the difference between MAKEFLAGS, .MAKEFLAGS and MAKE_FLAGS?</a> @@ -9516,7 +9539,7 @@ do?</a> <tbody> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.makeflags"></a><a name="idm77324560"></a><p><b>22.1.</b></p> +<a name="devfaq.makeflags"></a><a name="idm77173008"></a><p><b>22.1.</b></p> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and @@ -9532,7 +9555,7 @@ do?</a> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.make"></a><a name="idm77320592"></a><p><b>22.2.</b></p> +<a name="devfaq.make"></a><a name="idm77168912"></a><p><b>22.2.</b></p> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and @@ -9550,7 +9573,7 @@ do?</a> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.cc"></a><a name="idm77316112"></a><p><b>22.3.</b></p> +<a name="devfaq.cc"></a><a name="idm77164560"></a><p><b>22.3.</b></p> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and @@ -9568,7 +9591,7 @@ do?</a> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.bl3flags"></a><a name="idm77312016"></a><p><b>22.4.</b></p> +<a name="devfaq.bl3flags"></a><a name="idm77160336"></a><p><b>22.4.</b></p> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">BUILDLINK_LDFLAGS</code>, @@ -9581,7 +9604,7 @@ do?</a> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.bl3prefix"></a><a name="idm77309840"></a><p><b>22.5.</b></p> +<a name="devfaq.bl3prefix"></a><a name="idm77158160"></a><p><b>22.5.</b></p> </td> <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span> @@ -9597,7 +9620,7 @@ do?</a> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.master_sites"></a><a name="idm77306640"></a><p><b>22.6.</b></p> +<a name="devfaq.master_sites"></a><a name="idm77155088"></a><p><b>22.6.</b></p> </td> <td align="left" valign="top"><p>What does <code class="literal">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I @@ -9621,7 +9644,7 @@ do?</a> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.mailinglists"></a><a name="idm77298576"></a><p><b>22.7.</b></p> +<a name="devfaq.mailinglists"></a><a name="idm77147024"></a><p><b>22.7.</b></p> </td> <td align="left" valign="top"><p>Which mailing lists are there for package developers?</p></td> @@ -9646,7 +9669,7 @@ do?</a> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.documentation"></a><a name="idm77294864"></a><p><b>22.8.</b></p> +<a name="devfaq.documentation"></a><a name="idm77143184"></a><p><b>22.8.</b></p> </td> <td align="left" valign="top"><p>Where is the pkgsrc documentation?</p></td> @@ -9694,7 +9717,7 @@ do?</a> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="devfaq.too-much-time"></a><a name="idm77288336"></a><p><b>22.9.</b></p> +<a name="devfaq.too-much-time"></a><a name="idm77128464"></a><p><b>22.9.</b></p> </td> <td align="left" valign="top"><p>I have a little time to kill. What shall I do?</p></td> diff --git a/doc/pkgsrc.txt b/doc/pkgsrc.txt index e49dd169682..6c34af749b7 100644 --- a/doc/pkgsrc.txt +++ b/doc/pkgsrc.txt @@ -210,7 +210,8 @@ II. The pkgsrc developer's guide 13.5. Man page compression 13.6. Changing PLIST source with PLIST_SRC 13.7. Platform-specific and differing PLISTs - 13.8. Sharing directories between packages + 13.8. Build-specific PLISTs + 13.9. Sharing directories between packages 14. Buildlink methodology @@ -2911,7 +2912,8 @@ Table of Contents 13.5. Man page compression 13.6. Changing PLIST source with PLIST_SRC 13.7. Platform-specific and differing PLISTs - 13.8. Sharing directories between packages + 13.8. Build-specific PLISTs + 13.9. Sharing directories between packages 14. Buildlink methodology @@ -4156,7 +4158,8 @@ Table of Contents 13.5. Man page compression 13.6. Changing PLIST source with PLIST_SRC 13.7. Platform-specific and differing PLISTs -13.8. Sharing directories between packages +13.8. Build-specific PLISTs +13.9. Sharing directories between packages The PLIST file contains a package's "packing list", i.e. a list of files that belong to the package (relative to the ${PREFIX} directory it's been installed @@ -4179,7 +4182,7 @@ targets" for more information on this target. 13.3. Tweaking output of make print-PLIST -If you have used any of the *-dirs packages, as explained in Section 13.8, +If you have used any of the *-dirs packages, as explained in Section 13.9, "Sharing directories between packages", you may have noticed that make print-PLIST outputs a set of @comments instead of real @dirrm lines. You can also do this for specific directories and files, so that the results of that @@ -4299,7 +4302,23 @@ following files: * PLIST.common_end -13.8. Sharing directories between packages +13.8. Build-specific PLISTs + +Some packages decide to generate hard-to-guess file names during installation +that are hard to wire down. + +In such cases, you can set the GENERATE_PLIST variable to shell code terminated +(with a semicolon) that will output PLIST entries which will be appended to the +PLIST + +You can find one example in editors/xemacs: + + GENERATE_PLIST+= ${ECHO} bin/${DISTNAME}-`${WRKSRC}/src/xemacs -sd`.dmp ; + + +which will append something like bin/xemacs-21.4.23-54e8ea71.dmp to the PLIST. + +13.9. Sharing directories between packages A "shared directory" is a directory where multiple (and unrelated) packages install files. These directories were problematic because you had to add @@ -4316,6 +4335,8 @@ installation as usual, and also add an entry to the PLIST: @pkgdir path/to/empty/directory +or take a look at MAKE_DIRS and OWN_DIRS. + Chapter 14. Buildlink methodology Table of Contents |