[pkgsrc/trunk]: pkgsrc/doc/guide/files This file is unused for some time now....

[hubertf <hubertf%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/89890d5e201f
branches:  trunk
changeset: 483856:89890d5e201f
user:      hubertf <hubertf%pkgsrc.org@localhost>
date:      Sat Nov 20 13:11:36 2004 +0000

description:
This file is unused for some time now. Remove.

diffstat:

 doc/guide/files/features.xml |  1246 ------------------------------------------
 1 files changed, 0 insertions(+), 1246 deletions(-)

diffs (truncated from 1250 to 300 lines):

diff -r f205158e5620 -r 89890d5e201f doc/guide/files/features.xml
--- a/doc/guide/files/features.xml      Sat Nov 20 12:47:40 2004 +0000
+++ /dev/null   Thu Jan 01 00:00:00 1970 +0000
@@ -1,1246 +0,0 @@
-<!-- $NetBSD: features.xml,v 1.2 2004/10/22 00:24:48 hubertf Exp $ -->
-
-<chapter id="features"> <?dbhtml filename="features.html"?>
-<title>FAQs &amp; features of the package system</title>
-
-<sect1>
-<title>Packages using GNU autoconf</title>
-
-<para>
-If your package uses GNU autoconf created configure scripts, add the following
-to your package's <filename>Makefile</filename>:
-</para>
-
-<programlisting>GNU_CONFIGURE= yes</programlisting>
-
-<para>
-Note that this appends <quote>--prefix=${PREFIX}</quote> to
-<varname>CONFIGURE_ARGS</varname>, so you don't
-have to do that yourself, but may not be desired.
-</para>
-</sect1>
-
-
-<sect1>
-<title>Other distrib methods than .tar.gz</title>
-
-<para>
-If your package uses a different distribution method from
-<filename>.tar.gz</filename>, take a
-look at the package for <pkg>editors/sam</pkg>, which uses a gzipped shell archive
-(shar), but the quick solution is to set
-<varname>EXTRACT_SUFX</varname> to the name after the
-<varname>DISTNAME</varname> field, and add the following to your
-package's <filename>Makefile</filename>:
-</para>
-
-<programlisting>EXTRACT_SUFX=   .msg.gz
-EXTRACT_CMD=            zcat
-EXTRACT_BEFORE_ARGS=
-EXTRACT_AFTER_ARGS=     |sh</programlisting>
-</sect1>
-
-
-<sect1>
-<title>Packages not creating their own subdirectory</title>
-
-<para>
-Your package doesn't create a subdirectory for itself (like GNU software
-does, for instance), but extracts itself in the current directory: see
-<pkg>editors/sam</pkg> again, but the quick answer is:
-</para>
-
-<programlisting>WRKSRC=                ${WRKDIR}</programlisting>
-
-<para>
-Please note that the old:
-</para>
-
-<programlisting>NO_WRKSUBDIR=   yes</programlisting>
-
-<para>
-has been deprecated and should not be used.
-</para>
-</sect1>
-
-<sect1>
-<title>Custom configuration process</title>
-
-<para>
-Your package uses a weird Configure script, eg.
-<pkg>sysutils/top</pkg>. The quick answer is:
-</para>
-
-<programlisting>HAS_CONFIGURE=          yes
-CONFIGURE_SCRIPT=       Configure
-CONFIGURE_ARGS+=        netbsd13</programlisting>
-</sect1>
-
-
-<sect1>
-<title>Packages not building in their DISTNAME directory</title>
-
-<para>
-Your package builds in a different directory from its base
-<varname>DISTNAME</varname> (see <pkg>lang/tcl</pkg> and
-<pkg>x11/tk</pkg>).
-</para>
-
-<programlisting>WRKSRC=         ${WRKDIR}/${DISTNAME}/unix</programlisting>
-</sect1>
-
-
-<sect1>
-<title>How to fetch all distfiles at once</title>
-
-<para>
-You would like to download all the distfiles in a single batch from work or
-university, where you can't run a <command>make fetch</command>. There
-is an archive of distfiles on <ulink
-url="ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/";>ftp.NetBSD.org</ulink>,
-but downloading the entire directory may not be appropriate.
-</para>
-
-<para>
-The answer here is to do a <command>make fetch-list</command> in
-<filename>/usr/pkgsrc</filename>, carry the 
-resulting list to your machine at work/school and use it there If you don't
-have a NetBSD-compatible ftp(1) (like lukemftp) at work, don't forget to
-set <varname>FETCH_CMD</varname> to something that fetches a URL:
-</para>
-
-<para>
-At home:
-</para>
-
-<screen><prompt>%</prompt> <userinput>cd /usr/pkgsrc</userinput>
-<prompt>%</prompt> <userinput>make fetch-list FETCH_CMD=wget DISTDIR=/tmp/distfiles >/tmp/fetch.sh</userinput>
-<prompt>%</prompt> <userinput>scp /tmp/fetch.sh work:/tmp</userinput></screen>
-
-<para>
-At work:
-</para>
-
-<screen><prompt>%</prompt> <userinput>sh /tmp/fetch.sh</userinput></screen>
-
-<para>
-then tar up <filename>/tmp/distfiles</filename> and take it home.
-</para>
-
-<para>
-If you have a machine running NetBSD, and you want to get
-<emphasis>all</emphasis> distfiles
-(even ones that aren't for your machine architecture), you can do so by
-using the above-mentioned <command>make fetch-list</command> approach, or
-fetch the distfiles directly by running:
-</para>
-
-<screen><prompt>%</prompt> <userinput>make mirror-distfiles</userinput></screen>
-
-<para>
-If you even decide to ignore <varname>NO_{SRC,BIN}_ON_{FTP,CDROM}</varname>,
-then you can get everything by running:
-</para>
-
-<screen><prompt>%</prompt> <userinput>make fetch NO_SKIP=yes</userinput></screen>
-</sect1>
-
-
-<sect1>
-<title>How to fetch files from behind a firewall</title>
-
-<para>
-If you are sitting behind a firewall which does not allow direct connections
-to Internet hosts (i.e. non-NAT), you may specify the relevant proxy hosts.
-This is done using an environment variable in the form of a URL
-e.g. in Amdahl, the machine <quote>orpheus.amdahl.com</quote> is one of
-the firewalls, and it uses port 80 as the proxy port number. So the proxy
-environment variables are:
-</para>
-
-<programlisting>ftp_proxy=ftp://orpheus.amdahl.com:80/
-http_proxy=http://orpheus.amdahl.com:80/</programlisting>
-</sect1>
-
-
-<sect1>
-<title>If your patch contains an RCS ID</title>
-
-<para>
-See <xref linkend="components.patches"/> for information on how to
-remove RCS IDs from patch files.
-</para>
-</sect1>
-
-
-<sect1>
-<title>How to pull in variables from /etc/mk.conf</title>
-
-<para>
-The problem with package-defined variables that can be overridden via
-<varname>MAKECONF</varname> or <filename>/etc/mk.conf</filename> is that make(1) expands a variable as it is
-used, but evaluates preprocessor like statements (.if, .ifdef and
-.ifndef) as they are read.  So, to use any variable (which may be set
-in <filename>/etc/mk.conf</filename>) in one of the .if* statements, the file
-<filename>/etc/mk.conf</filename>
-must be included before that .if* statement.
-</para>
-
-<para>
-Rather than have a number of ad-hoc ways of including
-<filename>/etc/mk.conf</filename>,
-should it exist, or <varname>MAKECONF</varname>, should it exist, include the
-<filename>pkgsrc/mk/bsd.prefs.mk</filename> file in the package Makefile before any
-preprocessor-like .if, .ifdef, or .ifndef statements:
-</para>
-
-<programlisting>.include "../../mk/bsd.prefs.mk"
-
-.if defined(USE_MENUS)
-  ...
-.endif</programlisting>
-
-<para>
-If you wish to set the CFLAGS variable in /etc/mk.conf please make sure
-to use:
-
-<screen>CFLAGS+=       -your -flags</screen>
-
-Using <varname>CFLAGS=</varname> (ie without the <quote>+</quote>) may
-lead to problems with packages that need to add their own flags.  Also,
-you may want to take a look at the <pkg>devel/cpuflags</pkg> package if
-you're interested in optimization for the current CPU.
-</para>
-</sect1>
-
-<sect1>
-<title>Is there a mailing list for pkg-related discussion?</title>
-
-<para>
-Yes, <email>tech-pkg%NetBSD.org@localhost</email> is the list for discussing package
-related issues. To subscribe do:
-</para>
-
-<programlisting>% echo subscribe tech-pkg | mail majordomo%NetBSD.org@localhost</programlisting>
-</sect1>
-
-
-<sect1>
-<title>How do I tell <command>make fetch</command> to do passive FTP?</title>
-
-<para>
-This depends on which utility is used to retrieve distfiles. From
-<filename>bsd.pkg.mk</filename>, <varname>FETCH_CMD</varname> is assigned
-the first available command from the following list:
-</para>
-
-<programlisting>/usr/bin/fetch
-${LOCALBASE}/bsd/bin/ftp
-/usr/bin/ftp</programlisting>
-
-<para>
-On a default NetBSD install, this will be
-<filename>/usr/bin/ftp</filename>, which automatically
-tries passive connections first, and falls back to active connections if the
-server refuses to do passive. For the other tools, add the following to your
-<filename>/etc/mk.conf</filename> file:
-<varname>PASSIVE_FETCH=1</varname>.
-</para>
-
-<para>
-Having that option present will prevent
-<filename>/usr/bin/ftp</filename> from falling back to
-active transfers.
-</para>
-</sect1>
-
-
-<sect1>
-<title>Dependencies on other packages</title>
-
-<para>
-Your package may depend on some other package being present - and there are
-various ways of expressing this dependency. NetBSD supports the
-<varname>BUILD_DEPENDS</varname> and <varname>DEPENDS</varname> definitions,
-as well as dependencies via
-<filename>buildlink3.mk</filename> (see <!-- <xref
-linkend="buildlink3"/> -->).
-</para>
-
-<para>
-The basic difference between the two definitions is as follows: The
-<varname>DEPENDS</varname> definition registers that pre-requisite in the binary package,
-whilst the <varname>BUILD_DEPENDS</varname> definition does not.
-</para>
-
-<para>
-This means that if you only need a package present whilst you are building,
-it should be noted as a <varname>BUILD_DEPENDS</varname>.
-</para>
-
-<para>
-The format for a <varname>BUILD_DEPENDS</varname> and a
-<varname>DEPENDS</varname> definition is:
-</para>
-
-<programlisting>&lt;pre-req-package-name&gt;:../../&lt;category&gt;/&lt;pre-req-package&gt;</programlisting>
-
-<para>
-Please note that the <quote>pre-req-package-name</quote> may include any of the wildcard
-version numbers recognised by pkg_info(1).
-</para>
-
-<orderedlist>
-
-<listitem>
-<para>