Annotation of pkgsrc/doc/guide/files/binary.xml, revision 1.35
1.35 ! rillig 1: <!-- $NetBSD: binary.xml,v 1.34 2007/09/18 08:17:21 rillig Exp $ -->
1.1 grant 2:
3: <chapter id="binary">
4: <title>Creating binary packages</title>
5:
1.13 wiz 6: <sect1 id="building-a-single-binary-package">
1.1 grant 7: <title>Building a single binary package</title>
8:
1.25 wiz 9: <para>Once you have built and installed a package, you can create
10: a <emphasis>binary package</emphasis> which can be installed on
11: another system with &man.pkg.add.1;. This saves having to build
12: the same package on a group of hosts and wasting CPU time. It also
13: provides a simple means for others to install your package, should
14: you distribute it.</para>
15:
16: <para>To create a binary package, change into the appropriate
17: directory in pkgsrc, and run <command>make
18: package</command>:</para>
1.1 grant 19:
1.35 ! rillig 20: <screen>
! 21: &uprompt; <userinput>cd misc/figlet</userinput>
! 22: &uprompt; <userinput>make package</userinput>
! 23: </screen>
1.1 grant 24:
1.25 wiz 25: <para>This will build and install your package (if not already done),
26: and then build a binary package from what was installed. You can
27: then use the <command>pkg_*</command> tools to manipulate
28: it. Binary packages are created by default in
29: <filename>/usr/pkgsrc/packages</filename>, in the form of a
30: gzipped tar file. See <xref linkend="logs.package"/> for a
31: continuation of the above <filename
32: role="pkg">misc/figlet</filename> example.</para>
33:
34: <para>See <xref linkend="submit"/> for information on how to submit
35: such a binary package.</para>
1.1 grant 36: </sect1>
37:
1.13 wiz 38: <sect1 id="settings-for-creationg-of-binary-packages">
1.1 grant 39: <title>Settings for creation of binary packages</title>
40:
41: <para>See <xref linkend="build.helpful-targets"/>.</para>
42: </sect1>
43: </chapter>
CVSweb <webmaster@jp.NetBSD.org>