Import of pkgsrc-2014Q1
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: buildlink.xml,v 1.34 2013/04/21 15:20:46 wiz Exp $ -->
|
||||
<!-- $NetBSD: buildlink.xml,v 1.36 2013/07/30 07:14:09 wiz Exp $ -->
|
||||
|
||||
<chapter id="buildlink">
|
||||
<title>Buildlink methodology</title>
|
||||
@@ -126,6 +126,17 @@ BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0
|
||||
which Motif version will be used.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename>readline.buildlink3.mk</filename> checks for a
|
||||
system-provided GNU readline or editline (libedit) installation,
|
||||
or adds a dependency on <filename role="pkg">devel/readline</filename>,
|
||||
<filename role="pkg">devel/editline</filename>. The user can set
|
||||
<varname>READLINE_DEFAULT</varname> to choose readline implementation.
|
||||
If your package really needs GNU readline library, its Makefile
|
||||
should include <filename>devel/readline/buildlink3.mk</filename>
|
||||
instead of <filename>readline.buildlink3.mk</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename>oss.buildlink3.mk</filename> defines several
|
||||
variables that may be used by packages that use the
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: bulk.xml,v 1.10 2012/08/26 10:34:20 wiz Exp $ -->
|
||||
<!-- $NetBSD: bulk.xml,v 1.12 2013/12/31 19:27:06 dholland Exp $ -->
|
||||
|
||||
<chapter id="bulk">
|
||||
<title>Creating binary packages for everything in pkgsrc (bulk
|
||||
@@ -66,15 +66,15 @@ temporary filesystems, others must survive a sudden reboot.</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem><para>10 GB for the distfiles (read-write, remote, temporary)</para></listitem>
|
||||
<listitem><para>40 GB for the distfiles (read-write, remote, temporary)</para></listitem>
|
||||
|
||||
<listitem><para>10 GB for the binary packages (read-write, remote, permanent)</para></listitem>
|
||||
<listitem><para>30 GB for the binary packages (read-write, remote, permanent)</para></listitem>
|
||||
|
||||
<listitem><para>400 MB for the pkgsrc tree (read-only, remote, permanent)</para></listitem>
|
||||
<listitem><para>1 GB for the pkgsrc tree (read-only, remote, permanent)</para></listitem>
|
||||
|
||||
<listitem><para>5 GB for <filename>LOCALBASE</filename> (read-write, local, temporary for pbulk, permanent for old-bulk)</para></listitem>
|
||||
|
||||
<listitem><para>5 GB for the log files (read-write, remote, permanent)</para></listitem>
|
||||
<listitem><para>10 GB for the log files (read-write, remote, permanent)</para></listitem>
|
||||
|
||||
<listitem><para>5 GB for temporary files (read-write, local, temporary)</para></listitem>
|
||||
|
||||
@@ -329,15 +329,15 @@ fi
|
||||
<title>Disk space requirements</title>
|
||||
|
||||
<para>Currently, roughly the following requirements are valid for
|
||||
NetBSD 2.0/i386:</para>
|
||||
NetBSD 6.99/amd64:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>10 GB - distfiles (NFS ok)</para>
|
||||
<para>40 GB - distfiles (NFS ok)</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>8 GB - full set of all binaries (NFS ok)</para>
|
||||
<para>30 GB - full set of all binaries (NFS ok)</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
@@ -417,8 +417,7 @@ fi
|
||||
<step>
|
||||
|
||||
<para><filename>/usr/src</filename> (system sources,
|
||||
e. g. for <filename
|
||||
role="pkg">sysutils/aperture</filename>):</para>
|
||||
rarely used by packages if at all:</para>
|
||||
|
||||
<screen>&rprompt; <userinput>ln -s ../disk1/cvs .</userinput>
|
||||
&rprompt; <userinput>ln -s cvs/src-2.0 src</userinput></screen>
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: creating.xml,v 1.12 2012/10/03 22:14:01 wiz Exp $ -->
|
||||
<!-- $NetBSD: creating.xml,v 1.16 2014/01/18 20:18:50 wiz Exp $ -->
|
||||
|
||||
<chapter id="creating">
|
||||
<title>Creating a new pkgsrc package from scratch</title>
|
||||
@@ -136,23 +136,12 @@ settings that are typical of KDE packages.</para>
|
||||
<para>Python modules and programs packages are easily created using a
|
||||
set of predefined variables.</para>
|
||||
|
||||
<para>Most Python packages use either <quote>distutils</quote> or
|
||||
easy-setup (<quote>eggs</quote>).
|
||||
If the software uses <quote>distutils</quote>, set the
|
||||
<varname>PYDISTUTILSPKG</varname> variable to <quote>yes</quote> so
|
||||
pkgsrc will make use of this framework.
|
||||
<quote>distutils</quote> uses a script called <filename>setup.py</filename>,
|
||||
if the <quote>distutils</quote> driver is not called
|
||||
<filename>setup.py</filename>, set the <varname>PYSETUP</varname> variable
|
||||
to the name of the script.</para>
|
||||
|
||||
<para>
|
||||
If the default Python versions are not supported by the software, set the
|
||||
<varname>PYTHON_VERSIONS_ACCEPTED</varname> variable to the Python versions
|
||||
the software is known to work with, from the most recent to the older
|
||||
one, e.g.
|
||||
If some Python versions are not supported by the software, set the
|
||||
<varname>PYTHON_VERSIONS_INCOMPATIBLE</varname> variable to the Python versions
|
||||
that are not supported, e.g.
|
||||
<programlisting>
|
||||
PYTHON_VERSIONS_ACCEPTED= 31 27 26
|
||||
PYTHON_VERSIONS_INCOMPATIBLE= 26
|
||||
</programlisting></para>
|
||||
|
||||
<para>
|
||||
@@ -166,22 +155,43 @@ DISTNAME= foopymodule-1.2.10
|
||||
PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
|
||||
</programlisting></para>
|
||||
|
||||
<para>If it is an application, also include
|
||||
<quote><filename>../../lang/python/application.mk</filename></quote>
|
||||
before <quote>extension.mk</quote>.</para>
|
||||
|
||||
<para>If the packaged software, either it is an application or a module, is
|
||||
egg-aware, you only need to include
|
||||
<quote><filename>../../lang/python/egg.mk</filename></quote>.</para>
|
||||
|
||||
<para>In order to correctly set the path to the Python interpreter, use the
|
||||
<para>If it is an application, include
|
||||
<quote><filename>../../lang/python/application.mk</filename></quote>.
|
||||
In order to correctly set the path to the Python interpreter, use the
|
||||
<varname>REPLACE_PYTHON</varname> variable and set it to the list of files
|
||||
(paths relative to <varname>WRKSRC</varname>) that must be corrected.
|
||||
For example :
|
||||
For example:
|
||||
<programlisting>
|
||||
REPLACE_PYTHON= *.py
|
||||
</programlisting></para>
|
||||
|
||||
<para>Most Python packages use either <quote>distutils</quote> or
|
||||
easy-setup (<quote>eggs</quote>).
|
||||
If the software uses <quote>distutils</quote>, include
|
||||
<quote><filename>../../lang/python/distutils.mk</filename></quote>.
|
||||
so pkgsrc will use this framework.
|
||||
<quote>distutils</quote> uses a script called <filename>setup.py</filename>,
|
||||
if the <quote>distutils</quote> driver is not called
|
||||
<filename>setup.py</filename>, set the <varname>PYSETUP</varname> variable
|
||||
to the name of the script.</para>
|
||||
|
||||
<para>Otherwise, if the packaged software is egg-aware, you only need
|
||||
to include
|
||||
<quote><filename>../../lang/python/egg.mk</filename></quote>.</para>
|
||||
|
||||
<para>Some Python modules have separate distributions for Python-2.x
|
||||
and Python-3.x support. In pkgsrc this is handled by the
|
||||
<filename>versioned_dependencies.mk</filename> file. Set
|
||||
<varname>PYTHON_VERSIONED_DEPENDENCIES</varname> to the list of
|
||||
packages that should be depended upon and include
|
||||
<quote><filename>../../lang/python/versioned_dependencies.mk</filename></quote>,
|
||||
then the pkgsrc infrastructure will depend on the appropriate package
|
||||
version. For example:
|
||||
<programlisting>
|
||||
PYTHON_VERSIONED_DEPENDENCIES=dateutil dns
|
||||
</programlisting>
|
||||
Look inside <filename>versioned_dependencies.mk</filename> for a list
|
||||
of supported packages.</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
@@ -376,7 +386,7 @@ and tried again.</para>
|
||||
|
||||
<programlisting>
|
||||
[...]
|
||||
cc -o xpidl.o -c -DOSTYPE=\"NetBSD3\" -DOSARCH=\"NetBSD\" -I../../../dist/include/xpcom -I../../../dist/include -I/tmp/roland/pkgsrc/www/nvu/work.bacc/mozilla/dist/include/nspr -I/usr/X11R6/include -fPIC -DPIC -I/home/roland/pkg/include -I/usr/include -I/usr/X11R6/include -Wall -W -Wno-unused -Wpointer-arith -Wcast-align -Wno-long-long -pedantic -O2 -I/home/roland/pkg/include -I/usr/include -Dunix -pthread -pipe -DDEBUG -D_DEBUG -DDEBUG_roland -DTRACING -g -I/home/roland/pkg/include/glib/glib-1.2 -I/home/roland/pkg/lib/glib/include -I/usr/pkg/include/orbit-1.0 -I/home/roland/pkg/include -I/usr/include -I/usr/X11R6/include -include ../../../mozilla-config.h -DMOZILLA_CLIENT -Wp,-MD,.deps/xpidl.pp xpidl.c
|
||||
cc -o xpidl.o -c -DOSTYPE=\"NetBSD3\" -DOSARCH=\"NetBSD\" [...]
|
||||
In file included from xpidl.c:42:
|
||||
xpidl.h:53:24: libIDL/IDL.h: No such file or directory
|
||||
In file included from xpidl.c:42:
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: faq.xml,v 1.48 2011/07/31 08:48:22 spz Exp $ -->
|
||||
<!-- $NetBSD: faq.xml,v 1.50 2014/02/03 16:09:34 wiz Exp $ -->
|
||||
|
||||
<chapter id="faq"> <?dbhtml filename="faq.html"?>
|
||||
<title>Frequently Asked Questions</title>
|
||||
@@ -138,11 +138,6 @@ with each package.</para>
|
||||
methods: multiple CD-ROMs and network FTP/HTTP connections.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename role="pkg">pkgtools/xpkgwedge</filename>: Put X11
|
||||
packages someplace else (enabled by default).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename role="pkg">devel/cpuflags</filename>: Determine
|
||||
the best compiler flags to optimise code for your current
|
||||
@@ -156,6 +151,12 @@ etc:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para><filename role="pkg">pkgtools/pkgin</filename>: A package
|
||||
update tool similar to apt(1). Download, install, and upgrade
|
||||
binary packages easily.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename role="pkg">pkgtools/pkg_chk</filename>: Reports on
|
||||
packages whose installed versions do not match the latest pkgsrc
|
||||
@@ -202,16 +203,10 @@ etc:</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename role="pkg">pkgtools/rpm2pkg</filename>,
|
||||
<filename role="pkg">pkgtools/url2pkg</filename>: Aids in
|
||||
<para><filename role="pkg">pkgtools/url2pkg</filename>: Aids in
|
||||
converting to pkgsrc.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename role="pkg">pkgtools/gensolpkg</filename>: Convert
|
||||
pkgsrc to a Solaris package.</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
<para>Utilities for people maintaining pkgsrc (or: more obscure pkg
|
||||
@@ -272,7 +267,7 @@ enable this feature by adding the option
|
||||
distfile is found, pkgsrc will try to resume it.</para>
|
||||
|
||||
<para>You can also
|
||||
use a different program than the default &man.ftp.1; by changing the
|
||||
use a different program than the platform default program by changing the
|
||||
<varname>FETCH_USING</varname> variable. You can specify the program by
|
||||
using of ftp, fetch, wget or curl. Alternatively, fetching can be disabled
|
||||
by using the value manual. A value of custom disables the system defaults
|
||||
@@ -332,6 +327,26 @@ http_proxy=http://orpheus.amdahl.com:80/
|
||||
|
||||
<!-- ================================================================== -->
|
||||
|
||||
<sect1 id="fetch-https">
|
||||
<title>How to fetch files from HTTPS sites</title>
|
||||
|
||||
<para>Some fetch tools are not prepared to support HTTPS by default
|
||||
(for example, the one in NetBSD 6.0), or the one installed by the
|
||||
pkgsrc bootstrap (to avoid an openssl dependency that low in the
|
||||
dependency graph).</para>
|
||||
|
||||
<para>Usually you won't notice, because distribution files are
|
||||
mirrored weekly to <quote>ftp.NetBSD.org</quote>, but that might not
|
||||
be often enough if you are following pkgsrc-current. In that case, set
|
||||
<varname>FETCH_USING</varname> in your &mk.conf; file to
|
||||
<quote>curl</quote> or <quote>wget</quote>, which are both compiled
|
||||
with HTTPS support by default. Of course, these tools need to be
|
||||
installed before you can use them this way.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<!-- ================================================================== -->
|
||||
|
||||
<sect1 id="passive-ftp">
|
||||
<title>How do I tell <command>make fetch</command> to do passive FTP?</title>
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: fixes.xml,v 1.121 2013/05/26 18:21:46 wiz Exp $ -->
|
||||
<!-- $NetBSD: fixes.xml,v 1.123 2013/08/24 16:55:21 bsiegert Exp $ -->
|
||||
|
||||
<chapter id="fixes"> <?dbhtml filename="fixes.html"?>
|
||||
<title>Making your package work</title>
|
||||
@@ -133,6 +133,7 @@ INTERACTIVE_STAGE= configure install
|
||||
artistic artistic-2.0
|
||||
boost-license
|
||||
cc-by-sa-v3.0
|
||||
cc0-1.0-universal
|
||||
cddl-1.0
|
||||
cpl-1.0
|
||||
epl-v1.0
|
||||
@@ -443,6 +444,20 @@ DEPENDS+= ImageMagick>=6.0:../../graphics/ImageMagick
|
||||
linkend="security-handling"/> for more
|
||||
information.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>If the package depends on either one of two (or more)
|
||||
packages, specify the <quote>pre-req-package-name</quote> as a
|
||||
comma-separated list between curly braces.</para>
|
||||
|
||||
<para>As an example, take a package that depends on the Perl
|
||||
<quote>version</quote> module, which has been part of Perl
|
||||
itself since version 5.10.0. This either/or dependency is
|
||||
expressed as:</para>
|
||||
|
||||
<programlisting>
|
||||
DEPENDS+= {perl>=5.10.0,p5-version-[0-9]*}:../../devel/p5-version
|
||||
</programlisting>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>If your package needs files from another package to build,
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: getting.xml,v 1.31 2013/05/03 16:55:29 asau Exp $ -->
|
||||
<!-- $NetBSD: getting.xml,v 1.32 2013/11/07 08:52:43 jnemeth Exp $ -->
|
||||
|
||||
<chapter id="getting">
|
||||
<title>Where to get pkgsrc and how to keep it up-to-date</title>
|
||||
@@ -58,18 +58,18 @@ and dashes.</para>
|
||||
|
||||
<para>You can fetch the same files using FTP.</para>
|
||||
|
||||
<para>The tar file for the stable branch 2009Q1 is in the
|
||||
directory <filename>pkgsrc-2009Q1</filename> and is also called <ulink
|
||||
url="ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2009Q1/pkgsrc-2009Q1.tar.gz"><filename>pkgsrc-2009Q1.tar.gz</filename></ulink>.</para>
|
||||
<para>The tar file for the stable branch 2013Q1 is in the
|
||||
directory <filename>pkgsrc-2013Q1</filename> and is also called <ulink
|
||||
url="ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2013Q1/pkgsrc.tar.gz"><filename>pkgsrc.tar.gz</filename></ulink>.</para>
|
||||
|
||||
<para>To download a pkgsrc stable tarball, run:</para>
|
||||
|
||||
<screen>
|
||||
&uprompt; <userinput>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/<replaceable>pkgsrc-20xxQy</replaceable>/<replaceable>pkgsrc-20xxQy</replaceable>.tar.gz</userinput></screen>
|
||||
&uprompt; <userinput>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/<replaceable>pkgsrc-20xxQy</replaceable>/pkgsrc.tar.gz</userinput></screen>
|
||||
|
||||
<para>Where <replaceable>pkgsrc-20xxQy</replaceable> is the
|
||||
stable branch to be downloaded, for example,
|
||||
<quote>pkgsrc-2009Q1</quote>.</para>
|
||||
<quote>pkgsrc-2013Q1</quote>.</para>
|
||||
|
||||
<para>You can use fetch it also using "wget", "curl",
|
||||
or your web browser.</para>
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: introduction.xml,v 1.28 2013/03/31 09:08:06 obache Exp $ -->
|
||||
<!-- $NetBSD: introduction.xml,v 1.30 2013/08/22 13:54:51 ryoon Exp $ -->
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>What is pkgsrc?</title>
|
||||
@@ -190,7 +190,7 @@ minutes!</para>
|
||||
</row>
|
||||
<row>
|
||||
<entry><ulink url="http://www.mirbsd.org/">MirBSD</ulink></entry>
|
||||
<entry align="center">Aug 2011</entry>
|
||||
<entry align="center">Jan 2011</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><ulink url="http://www.minix3.org/">Minix3</ulink></entry>
|
||||
@@ -200,6 +200,10 @@ minutes!</para>
|
||||
<entry><ulink url="http://cygwin.com/">Cygwin</ulink></entry>
|
||||
<entry align="center">Mar 2013</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><ulink url="http://www.debian.org/ports/kfreebsd-gnu/">GNU/kFreeBSD</ulink></entry>
|
||||
<entry align="center">Jul 2013</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: platforms.xml,v 1.81 2013/03/08 12:08:08 obache Exp $ -->
|
||||
<!-- $NetBSD: platforms.xml,v 1.84 2013/11/15 10:11:47 asau Exp $ -->
|
||||
|
||||
<chapter id="platforms">
|
||||
<title>Using pkgsrc on systems other than &os;</title>
|
||||
@@ -23,7 +23,7 @@
|
||||
<para>Installing the bootstrap kit from source should be as simple as:</para>
|
||||
|
||||
<screen>
|
||||
&rprompt; <userinput>env CVS_RSH=ssh cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout pkgsrc</userinput>
|
||||
&rprompt; <userinput>env CVS_RSH=ssh cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</userinput>
|
||||
&rprompt; <userinput>cd pkgsrc/bootstrap</userinput>
|
||||
&rprompt; <userinput>./bootstrap</userinput>
|
||||
</screen>
|
||||
@@ -150,6 +150,16 @@
|
||||
</orderedlist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="gnukfreebsd">
|
||||
<title>GNU/kFreeBSD</title>
|
||||
|
||||
<para>Debian GNU/kFreeBSD is the only GNU/kFreeBSD distribution now.
|
||||
Debian GNU/kFreeBSD 7.0 or later is tested and supported.</para>
|
||||
|
||||
<para> You should install ncurses (libncurses and libncurses-dev)
|
||||
packages.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="interix">
|
||||
<title>Interix</title>
|
||||
|
||||
@@ -460,6 +470,34 @@ ICCBASE= /opt/intel/cc/10.1.008
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="mirbsd">
|
||||
<title>MirBSD</title>
|
||||
|
||||
<para>pkgsrc has been tested on MirBSD #10-current (2011 and newer).
|
||||
Older versions might also work. Releases before #10 are not
|
||||
supported.</para>
|
||||
|
||||
<para>The package tools of the (older) native ports tree,
|
||||
<ulink url="//www.mirbsd.org/ports.htm">MirPorts</ulink>,
|
||||
have the same names as the ones used by pkgsrc. Care should be taken
|
||||
that the right tools are used. When installing packages from source,
|
||||
use the <filename>bmake</filename> command for pkgsrc and
|
||||
<filename>mmake</filename> for MirPorts.</para>
|
||||
|
||||
<para>pkgsrc and MirPorts use the same location for the package
|
||||
database, <filename>/var/db/pkg</filename>. It is strongly recommended
|
||||
to use <filename>/usr/pkg/db</filename> instead, so that the pkgsrc
|
||||
tree is self-contained. This is also the default setting used in the
|
||||
binary package builds.</para>
|
||||
|
||||
<para>Binary packages for MirBSD/i386 can be found on the pkgsrc ftp
|
||||
server. The bootstrap kit there already contains the
|
||||
<command>pkgin</command> package manager. See the
|
||||
<ulink url="https://www.mirbsd.org/pkgsrc.htm">pkgsrc on MirOS</ulink>
|
||||
page for more details.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="openbsd">
|
||||
<title>OpenBSD</title>
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<!-- $NetBSD: submit.xml,v 1.26 2012/06/07 08:15:55 wiz Exp $ -->
|
||||
<!-- $NetBSD: submit.xml,v 1.28 2014/02/25 02:30:06 mspo Exp $ -->
|
||||
|
||||
<chapter id="submit"> <?dbhtml filename="submit.html"?>
|
||||
<title>Submitting and Committing</title>
|
||||
@@ -87,7 +87,7 @@
|
||||
not the same as your NetBSD login name. The target also automatically
|
||||
removes possibly existing entries for the package in the
|
||||
<filename>TODO</filename> file. Don't forget to commit
|
||||
the changes, e.g. by using <command>make changes-entry-commit</command>!
|
||||
the changes, e.g. by using <command>make commit-changes-entry</command>!
|
||||
If you are not using a checkout directly from cvs.NetBSD.org, but e.g.
|
||||
a local copy of the repository, you can set USE_NETBSD_REPO=yes. This
|
||||
makes the cvs commands use the main repository.
|
||||
@@ -114,6 +114,9 @@ you can check by running <quote>cvs status</quote>. An example:</para>
|
||||
&uprompt; cd ..
|
||||
&uprompt; vi Makefile # add SUBDIRS+=pkgname line
|
||||
&uprompt; cvs commit Makefile
|
||||
&uprompt; cd pkgname
|
||||
&uprompt; make CTYPE=Added changes-entry
|
||||
&uprompt; make commit-changes-entry
|
||||
</programlisting>
|
||||
|
||||
<para>The commit message of the initial import should include part of the
|
||||
|
||||
Reference in New Issue
Block a user