Automatic conversion of the NetBSD pkgsrc CVS module, use with care
Find a file
2003-06-07 14:47:16 +00:00
archivers s|/usr/pkg|@PREFIX@|g, so that the pre-configure target replaces the prefix 2003-06-06 10:11:15 +00:00
audio Truncate COMMENT to under 70 characters 2003-06-07 14:47:16 +00:00
benchmarks Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
biology Use mk/gcc.buildlink2.mk rather than gcc/buildlink2.mk so lang/gcc3 2003-06-02 14:05:00 +00:00
cad add py-MyHDL 2003-06-05 18:52:00 +00:00
chat Make INCOMPAT_CURSES pick up netbsd 1.6.1 correctly 2003-06-06 16:42:33 +00:00
comms Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
converters Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
cross Use mk/gcc.buildlink2.mk rather than gcc/buildlink2.mk so lang/gcc3 2003-06-02 14:05:00 +00:00
databases Update p5-DBIx-SearchBuilder to 0.84 2003-06-06 12:00:06 +00:00
devel Truncate COMMENT to under 70 characters 2003-06-07 14:47:16 +00:00
distfiles These files belong to $MASTER_SITE_LOCAL - moved them there! 2000-12-05 00:23:05 +00:00
doc Note revision bump for ettercap to 2. 2003-06-07 10:43:40 +00:00
editors Truncate COMMENT to under 70 characters 2003-06-07 14:47:16 +00:00
emulators Merge two patches fixing the same file (doscmd_loader.c); they were causing 2003-06-06 11:55:06 +00:00
finance Bump revisions following the guile14's threaded fix. 2003-06-05 05:01:54 +00:00
fonts Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
games Truncate COMMENT to under 70 characters 2003-06-07 14:47:16 +00:00
graphics Truncate COMMENT to under 70 characters 2003-06-07 14:47:16 +00:00
ham Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
inputmethod Update the MASTER_SITES path. 2003-06-04 00:32:14 +00:00
lang Add NetBSD RCS tags. 2003-06-07 14:37:01 +00:00
licenses Whitespace cleanup. 2003-05-19 06:05:07 +00:00
mail Update sylpheed to 0.9.2, from email on sylpheed list: 2003-06-06 07:03:51 +00:00
math update to 4.2.83 2003-06-06 18:26:50 +00:00
mbone Add & enable rtptools. 2003-05-07 20:53:25 +00:00
meta-pkgs Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
misc Use ${PREFIX} instead of hardcoding /usr/pkg. 2003-06-06 09:42:45 +00:00
mk if CC is defined, add it to MAKE_ENV 2003-06-07 09:22:37 +00:00
net Fix crash in -current: a thread was trying to wait for a condition using an 2003-06-07 10:42:26 +00:00
news Use mk/gcc.buildlink2.mk rather than gcc/buildlink2.mk so lang/gcc3 2003-06-02 14:05:00 +00:00
packages Add .cvsignore to stop cvs update listing every distfile and more 1999-11-24 11:53:24 +00:00
parallel Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
pkgtools Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
print Enable handling of PDF v1.3 files in dvipdfm, as per the change to the 2003-06-05 11:37:29 +00:00
security Update: 2003-06-06 17:09:05 +00:00
shells Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages. 2003-06-02 01:15:31 +00:00
sysutils Truncate COMMENT to under 70 characters 2003-06-07 14:47:16 +00:00
templates Fix the location of DESCR for the readme files 2001-11-03 03:26:08 +00:00
textproc Truncate COMMENT to under 70 characters 2003-06-07 14:47:16 +00:00
time add gdeskcal 2003-06-05 19:36:08 +00:00
wm Include "Xft2" buildlink2 glue code to fix build problems on XFree86 4.2.x 2003-06-04 08:56:46 +00:00
www Truncate COMMENT to under 70 characters 2003-06-07 14:47:16 +00:00
x11 Add some glue code so that the code which collects statistics for 2003-06-05 21:29:32 +00:00
Makefile Drop trailing whitespace. Ok'ed by wiz. 2003-05-06 17:40:18 +00:00
Packages.txt Add MASTER_SITE_GNUSTEP, MASTER_SITE_R_CRAN, MASTER_SITE_SUSE, 2003-06-05 17:32:13 +00:00
pkglocate Use "printf" instead of "echo -n" because it's more portable. 2003-05-31 14:20:46 +00:00
README Drop trailing whitespace. Ok'ed by wiz. 2003-05-06 17:40:18 +00:00

$NetBSD: README,v 1.15 2003/05/06 17:40:18 jmmv 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/bsd.pkg.defaults.mk gives
the defaults which are used in pkgsrc.  This file can be used as a
guide to set values in /etc/mk.conf - it is only necessary to set
values where they differ from the defaults.

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 directory.