Remove old method of creating pkg-plist. These methods will not work with staging support as nothing will get installed to the host system.
This commit is contained in:
parent
173280dbc5
commit
a683914c21
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=43155
1 changed files with 0 additions and 30 deletions
|
@ -10293,10 +10293,6 @@ etc/orbit.conf.sample
|
|||
based upon the version of dependent software used (e.g., ports
|
||||
which generate docs with
|
||||
<application>Javadoc</application>).</para>
|
||||
|
||||
<para>Note that the <buildtarget>makeplist</buildtarget> target can
|
||||
be used for ports that support staging to display the package
|
||||
list.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 xml:id="plist-autoplist">
|
||||
|
@ -10318,32 +10314,6 @@ etc/orbit.conf.sample
|
|||
libraries installed by the port should be listed as specified
|
||||
in the <link linkend="porting-shlibs">shared libraries</link>
|
||||
section.</para>
|
||||
|
||||
<para>Alternatively, use the <command>plist</command> script in
|
||||
<filename>/usr/ports/Tools/scripts/</filename> to build the
|
||||
package list automatically.</para>
|
||||
|
||||
<para>The first step is the same as above: take the first three
|
||||
lines, that is, <command>mkdir</command>,
|
||||
<command>mtree</command> and <command>make depends</command>.
|
||||
Then build and install the port:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>make install PREFIX=/var/tmp/`make -V PORTNAME`</userinput></screen>
|
||||
|
||||
<para>And let <command>plist</command> create the
|
||||
<filename>pkg-plist</filename> file:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/usr/ports/Tools/scripts/plist -Md -m `make -V MTREE_FILE` /var/tmp/`make -V PORTNAME` > pkg-plist</userinput></screen>
|
||||
|
||||
<para>The packing list still has to be tidied up by hand as
|
||||
stated above.</para>
|
||||
|
||||
<para>Another tool that might be used to create an initial
|
||||
<filename>pkg-plist</filename> is
|
||||
<package>ports-mgmt/genplist</package>. As
|
||||
with any automated tool, the resulting
|
||||
<filename>pkg-plist</filename> should be checked and manually
|
||||
edited as needed.</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
|
Loading…
Reference in a new issue