Automatic conversion of the NetBSD pkgsrc CVS module, use with care
Find a file
lukem 7fb5bf88b1 newapc driver: chop any trailing `:'s off the end of APC_F_MINUTES fields;
specifically the RUNTIME field on my SmartUPS-1400.
2001-11-20 14:53:03 +00:00
archivers Remove post-build target designed to make the build fail for reasons 2001-11-06 22:10:21 +00:00
audio - Fix file I/O on alpha. Only RIFF(PCM) is tested. 2001-11-18 15:03:39 +00:00
benchmarks Move pkg/ files into package's toplevel directory 2001-10-31 22:52:58 +00:00
biology Replace "${GTAR} cf - . | (cd ... ; ${GTAR} xf - )" pipelines with a 2001-11-14 14:47:53 +00:00
cad add and enable gerbv, gnucap, and mcalc. 2001-11-15 04:00:22 +00:00
chat Respect ${CONFDIR} and use the common INSTALL/DEINSTALL scripts instead of 2001-11-19 21:05:55 +00:00
comms Adjust format a bit: 2001-11-11 06:17:26 +00:00
converters Update MASTER_SITES and HOMEPAGE, per pkg/14427. 2001-11-02 18:16:46 +00:00
cross Move pkg/ files into package's toplevel directory 2001-10-31 22:03:21 +00:00
databases Note addition of databases/php4-odbc. 2001-11-19 22:58:12 +00:00
devel Initial import of p5-IPC-ShareLite 2001-11-20 08:04:50 +00:00
distfiles These files belong to $MASTER_SITE_LOCAL - moved them there! 2000-12-05 00:23:05 +00:00
editors Add plan9 to CATEGORIES like in the other packages that were once in 2001-11-18 19:17:05 +00:00
emulators Adjust format a bit: 2001-11-11 06:17:26 +00:00
finance Replace "${GTAR} cf - . | (cd ... ; ${GTAR} xf - )" pipelines with a 2001-11-14 14:47:53 +00:00
fonts Add plan9 to CATEGORIES like in the other packages that were once in 2001-11-18 19:17:05 +00:00
games Use the general INSTALL/DEINSTALL scripts instead of the homegrown ones. 2001-11-19 23:33:03 +00:00
graphics kdelibs2/buildlink.mk no longer pulls in tiff/buildlink.mk which is needed 2001-11-16 05:17:34 +00:00
ham Move pkg/ files into package's toplevel directory 2001-10-31 20:59:00 +00:00
japanese Don't use MAKE_FLAGS in MAKE_ENV, reported by Yuji Yamano in pr pkg/14536 and 2001-11-18 12:21:05 +00:00
lang Replace "${GTAR} cf - . | (cd ... ; ${GTAR} xf - )" pipelines with a 2001-11-14 14:47:53 +00:00
licenses VMWare license in preparation for the package in emulators/vmware. 2001-07-07 14:24:21 +00:00
mail Adapt to use shared INSTALL/DEINSTALL scripts by using the logic in 2001-11-19 16:23:08 +00:00
math Fixups to PLIST 2001-11-14 13:12:22 +00:00
mbone Move pkg/ files into package's toplevel directory 2001-10-31 20:59:00 +00:00
meta-pkgs Move pkg/ files into package's toplevel directory 2001-10-31 20:59:00 +00:00
misc Use the standard auto_ptr implementation in the new toolchain case. This 2001-11-15 23:38:54 +00:00
mk For completeness, add a SUPPORT_FILES_PERMS that acts like CONF_FILES_PERMS 2001-11-19 23:33:52 +00:00
net Strongly buildlinkify and libtoolize (NetBSD's interesting contributions to 2001-11-19 19:39:04 +00:00
news Move pkg/ files into package's toplevel directory 2001-10-31 20:59:00 +00:00
packages Add .cvsignore to stop cvs update listing every distfile and more 1999-11-24 11:53:24 +00:00
parallel Move pkg/ files into package's toplevel directory 2001-10-31 22:52:58 +00:00
pkgtools Set minimum required Perl version 5.6.0 because older version don't work. 2001-11-19 08:03:37 +00:00
print Adapt to use shared INSTALL/DEINSTALL scripts by using the logic in 2001-11-19 16:23:08 +00:00
security Mark as USE_BUILDLINK_ONLY. 2001-11-19 20:13:23 +00:00
shells Move pkg/ files into package's toplevel directory 2001-10-31 22:18:56 +00:00
sysutils newapc driver: chop any trailing `:'s off the end of APC_F_MINUTES fields; 2001-11-20 14:53:03 +00:00
templates Fix the location of DESCR for the readme files 2001-11-03 03:26:08 +00:00
textproc Add and enable source-highlight 2001-11-19 00:00:52 +00:00
time Strongly buildlinkify, and make this package work on Solaris by following 2001-11-15 07:58:50 +00:00
wm scwm has been broken for over a year now (because it doesn't work with 2001-11-09 00:43:12 +00:00
www Adapt to use shared INSTALL/DEINSTALL scripts by using the logic in 2001-11-19 16:23:08 +00:00
x11 Fix build problems with packages that use artsc-config. The -I option was 2001-11-19 17:48:08 +00:00
Makefile Use better expressions for grep, to avoid tagging non-IPv6 enabled packages 2001-07-17 13:11:51 +00:00
Packages.txt Note that to handle creating new users/groups for a package, you should use 2001-11-19 16:28:03 +00:00
pkglocate Apply mods from PR 14495, from Ryo HAYASAKA (ryoh@jaist.ac.jp), so that 2001-11-07 22:11:13 +00:00
README update a bit 2001-06-06 19:41:05 +00:00
TODO Added the gnome Nautilus file manager to be made into a pkg 2001-10-30 14:17:19 +00:00

$NetBSD: README,v 1.12 2001/06/06 19:41:05 hubertf Exp $

Welcome to the NetBSD Packages Collection
=========================================

In brief, the NetBSD Packages Collection is a set of software
utilities and libraries which have been ported to NetBSD.

The packages collection software can retrieve the software from its
home site, assuming you are connected in some way to the Internet,
verify its integrity, apply any patches, configure the software for
NetBSD, and build it.  Any prerequisite software will also be built
and installed for you.  Installation and de-installation of software
is managed by the packaging utilities.

The packages collection is made into a tar_file every week: 

	ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz

and you can sup the pkgsrc tree using the `pkgsrc' name for the
collection.

The pkgsrc tree is laid out in various categories, and, within that,
the various packages themselves.

You need to have root privileges to install packages.  We are looking
at ways to remove this restriction.

+ To install a package on your system, you need to change into the
directory of the package, and type "make install".

+ If you've made a mistake, and decided that you don't want that
package on your system, then type "pkg_delete <pkg-name>", or "make
deinstall" while in the directory for the package.

+ To find out all the packages that you have installed on your system,
type "pkg_info".

+ To remove the work directory, type "make clean", and "make
clean-depends" will clean up any working directories for other
packages that are built in the process of making your package.

+ Optionally, you can periodically run "make clean" from the top
level pkgsrc directory. This will delete extracted and built files,
but will not affect the retreived source sets in pkgsrc/distfiles.

+ You can set variables to customise the behaviour (where packages are
installed, various options for individual packages etc), by setting
variables in /etc/mk.conf.  The pkgsrc/mk/mk.conf.example file
provides some examples for customisation.

The best way to find out what packages are in the collection is to
move to the top-level pkgsrc directory (this will usually be
/usr/pkgsrc), and type "make readme".  This will create a file called
README.html in the top-level pkgsrc directory, and also in all
category and package directories.  You can then see what packages are
available, along with a short (one-line) comment about the function of
the package, and a pointer to a fuller description, by using a browser
like lynx (see pkgsrc/www/lynx) or Mozilla (pkgsrc/www/mozilla), or
Communicator.  This is also available online as
ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/README.html.

Another way to find out what packages are in the collection is to
move to the top-level pkgsrc directory and type "make index". This
will create pkgsrc/INDEX which can be viewed via "make print-index | more".
You can also search for particular packages or keywords via
"make search key=<somekeyword>".

It is also possible to use the packaging software to install
pre-compiled binary packages by typing "pkg_add <URL-of-binary-pkg>". 
To see what binary packages are available, see:

	ftp://ftp.netbsd.org/pub/NetBSD/packages/<release>/<arch>/All/

where <release> is the NetBSD release, and <arch> is the hardware
architecture.

One limitation of using binary packages provided from ftp.netbsd.org
is that all mk.conf options were set to the defaults at compile time.
LOCALBASE, in particular, defaults to /usr/pkg, so non-X binaries
will be installed in /usr/pkg/bin, man pages will be installed in
/usr/pkg/man...

When a packaged tool has major compile time choices, such as support
for multiple graphic toolkit libraries, the different options may
be available as separate packages.

For more information on the packages collection see the file
Packages.txt file in the same place where you found this README,
usually in the top-level pkgsrc dir.
directory.