Automatic conversion of the NetBSD pkgsrc CVS module, use with care
Find a file
jlam a68e218eca Older 2.2.x release of libmcrypt provided for those apps for which the
newer libmcrypt (>=2.4.x) seem to cause core dumps.

Import approved by Alistair <agc@netbsd.org>.
2002-04-12 18:59:36 +00:00
archivers Use "suse_linux/Makefile.application" to pick correct SuSE packages. 2002-04-04 12:29:46 +00:00
audio Use "suse_linux/Makefile.application" to pick correct SuSE packages. 2002-04-04 12:29:46 +00:00
benchmarks regen (hi jason!) 2002-04-05 11:11:44 +00:00
biology Include x11.buildlink.mk 2001-12-06 04:30:09 +00:00
cad add magic 2002-04-06 21:39:34 +00:00
chat Allow compiling in perl support for scripts. 2002-04-12 01:50:34 +00:00
comms Integrate patch-aa: LP64 fixes. 2002-04-02 20:27:40 +00:00
converters Update xlhtml package to 0.4.9.3 with HOMEPAGE and MASTER_SITES updates. 2002-04-08 15:04:03 +00:00
cross Make `dllwrap' (pkg/16156) 2002-04-05 18:55:26 +00:00
databases Ahh, the pitfalls of including bsd.*.mk. Keep up with NetBSD-1.5ZC, and 2002-04-11 16:16:48 +00:00
devel Build C++ library, too. 2002-04-12 14:12:18 +00:00
distfiles These files belong to $MASTER_SITE_LOCAL - moved them there! 2000-12-05 00:23:05 +00:00
editors Updated abiword-personal to 0.99.5 2002-04-12 14:32:50 +00:00
emulators Back out previous. Wine won't be able to run any nontrivial apps on 2002-04-12 17:45:43 +00:00
finance Give all packages which depend on "png" a version bump, and update 2002-03-13 17:36:35 +00:00
fonts Add and enable mozilla-fonts. 2002-04-09 13:18:07 +00:00
games Update to 3.0.0. Now uses gtk2 instead of gtk (first pkg in pkgsrc -- yeah!) :) 2002-04-06 18:58:32 +00:00
graphics Move the inclusion of Makefile.common below the definition of 2002-04-10 01:32:22 +00:00
ham Introduce new framework for handling info files generation and installation. 2002-02-18 15:14:00 +00:00
japanese Correct an invalid continuation. 2002-04-10 14:25:48 +00:00
lang Buildlink magic for guile. 2002-04-12 13:00:27 +00:00
licenses Mention ms-ttf-license in the list of ACCEPTABLE_LICENCES. 2002-03-06 17:05:30 +00:00
mail Update to 0.51. From the changelog: 2002-04-07 06:56:34 +00:00
math Add dependency on guile. It used to be pulled in incidentally from the 2002-04-12 13:02:52 +00:00
mbone Move pkg/ files into package's toplevel directory 2001-10-31 20:59:00 +00:00
meta-pkgs Give all packages which depend on "png" a version bump, and update 2002-03-13 17:36:35 +00:00
misc Add an additional check whether the display as set in the DISPLAY 2002-04-08 13:25:00 +00:00
mk Add note explaining when x11.buildlink.mk should be used. 2002-04-12 14:06:46 +00:00
net Add and enable bpalogin 2002-04-12 08:21:42 +00:00
news Fix typo (and bulk build). 2002-04-06 19:43:11 +00:00
packages Add .cvsignore to stop cvs update listing every distfile and more 1999-11-24 11:53:24 +00:00
parallel Explicitly set PVM_ROOT to fix installation stage. This is due to the change in 2002-02-07 10:49:07 +00:00
pkgtools The location of postgres.h and utils/builtins.h has moved to 2002-04-08 16:26:15 +00:00
print switch to using freetype2; should close pkg/16051 2002-04-10 12:17:39 +00:00
security Older 2.2.x release of libmcrypt provided for those apps for which the 2002-04-12 18:59:36 +00:00
shells Imagine my surprise when this failed to build on my -current shark. 2002-04-11 15:26:19 +00:00
sysutils Move comment in such a way that make doesn't stumble over it. 2002-04-11 22:00:25 +00:00
templates Fix the location of DESCR for the readme files 2001-11-03 03:26:08 +00:00
textproc mark as broken on alpha 2002-04-11 01:56:24 +00:00
time Fix typo in last commit. 2002-03-22 13:26:22 +00:00
wm Updated fvwm2 to 2.4.7 2002-04-12 09:09:08 +00:00
www Give PHP4 distfile a make variable name. 2002-04-12 17:59:57 +00:00
x11 Several changes: 2002-04-12 13:20:01 +00:00
Makefile replace some leading spaces with leading tabs. 2001-12-17 02:33:46 +00:00
Packages.txt If it is respectively' then I guess that 2.0-compatible' and 2002-04-02 21:04:31 +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 sentence which used to talk about mk.conf.example to explain the 2001-12-03 21:33:56 +00:00
TODO We have autoconf-2.52 in autoconf-devel. 2002-03-18 12:50:23 +00:00

$NetBSD: README,v 1.13 2001/12/03 21:33:56 agc 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 dir.
directory.