[BACK]Return to binary.xml CVS log [TXT][DIR] Up to [cvs.NetBSD.org] / pkgsrc / doc / guide / files
File: [cvs.NetBSD.org] / pkgsrc / doc / guide / files / binary.xml (download)

Revision 1.34, Tue Sep 18 08:17:21 2007 UTC (16 years, 7 months ago) by rillig
Branch: MAIN
CVS Tags: pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1, pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3, pkgsrc-2015Q2-base, pkgsrc-2015Q2, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4, pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2, pkgsrc-2014Q1-base, pkgsrc-2014Q1, pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2, pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4, pkgsrc-2012Q3-base, pkgsrc-2012Q3, pkgsrc-2012Q2-base, pkgsrc-2012Q2, pkgsrc-2012Q1-base, pkgsrc-2012Q1, pkgsrc-2011Q4-base, pkgsrc-2011Q4, pkgsrc-2011Q3-base, pkgsrc-2011Q3, pkgsrc-2011Q2-base, pkgsrc-2011Q2, pkgsrc-2011Q1-base, pkgsrc-2011Q1, pkgsrc-2010Q4-base, pkgsrc-2010Q4, pkgsrc-2010Q3-base, pkgsrc-2010Q3, pkgsrc-2010Q2-base, pkgsrc-2010Q2, pkgsrc-2010Q1-base, pkgsrc-2010Q1, pkgsrc-2009Q4-base, pkgsrc-2009Q4, pkgsrc-2009Q3-base, pkgsrc-2009Q3, pkgsrc-2009Q2-base, pkgsrc-2009Q2, pkgsrc-2009Q1-base, pkgsrc-2009Q1, pkgsrc-2008Q4-base, pkgsrc-2008Q4, pkgsrc-2008Q3-base, pkgsrc-2008Q3, pkgsrc-2008Q2-base, pkgsrc-2008Q2, pkgsrc-2008Q1-base, pkgsrc-2008Q1, pkgsrc-2007Q4-base, pkgsrc-2007Q4, pkgsrc-2007Q3-base, pkgsrc-2007Q3, cwrapper, cube-native-xorg-base, cube-native-xorg
Changes since 1.33: +1 -587 lines 

Moved the description of bulk builds into their own chapter. A new
section covering the pbulk system will be added soon.

<!-- $NetBSD: binary.xml,v 1.34 2007/09/18 08:17:21 rillig Exp $ -->

<chapter id="binary">
  <title>Creating binary packages</title>

  <sect1 id="building-a-single-binary-package">
    <title>Building a single binary package</title>

    <para>Once you have built and installed a package, you can create
    a <emphasis>binary package</emphasis> which can be installed on
    another system with &man.pkg.add.1;. This saves having to build
    the same package on a group of hosts and wasting CPU time. It also
    provides a simple means for others to install your package, should
    you distribute it.</para>

    <para>To create a binary package, change into the appropriate
    directory in pkgsrc, and run <command>make
    package</command>:</para>

    <screen>
&rprompt; <userinput>cd misc/figlet</userinput>
&rprompt; <userinput>make package</userinput>
    </screen>

    <para>This will build and install your package (if not already done),
    and then build a binary package from what was installed. You can
    then use the <command>pkg_*</command> tools to manipulate
    it. Binary packages are created by default in
    <filename>/usr/pkgsrc/packages</filename>, in the form of a
    gzipped tar file. See <xref linkend="logs.package"/> for a
    continuation of the above <filename
    role="pkg">misc/figlet</filename> example.</para>

    <para>See <xref linkend="submit"/> for information on how to submit
    such a binary package.</para>
  </sect1>

  <sect1 id="settings-for-creationg-of-binary-packages">
    <title>Settings for creation of binary packages</title>

    <para>See <xref linkend="build.helpful-targets"/>.</para>
  </sect1>
</chapter>