Automatic conversion of the NetBSD pkgsrc CVS module, use with care
Find a file
2003-01-25 13:59:05 +00:00
archivers Fix typo in last commit. 2003-01-21 14:22:31 +00:00
audio Update to 1.3.3. From the changelog: 2003-01-24 20:21:19 +00:00
benchmarks Make it build on Darwin again. Darwin have not in_addr_t. 2003-01-06 13:32:32 +00:00
biology Fix thinko, /usr -> ${PREFIX}. 2002-12-01 20:25:39 +00:00
cad Use buildlink2. 2003-01-25 12:48:40 +00:00
chat Update to 1.4.10. Bug fixes. 2003-01-25 04:09:15 +00:00
comms Install documentation. Bump PKGREVISION to 1. 2003-01-23 22:47:43 +00:00
converters Update from 2.12 to 2.16. 2003-01-09 15:49:17 +00:00
cross Replace "true" by "${TRUE}". 2002-12-09 16:01:10 +00:00
databases we need bsd.pkg.install.mk if we want to use it. 2003-01-24 04:05:22 +00:00
devel Bump the dependency to the latest version (0.19nb1). This isn't strictly 2003-01-25 12:40:23 +00:00
distfiles These files belong to $MASTER_SITE_LOCAL - moved them there! 2000-12-05 00:23:05 +00:00
doc Make sure that the correct guile program (guile14) is being invoked, and 2003-01-25 12:34:41 +00:00
editors create directories, then install files. 2003-01-25 03:10:36 +00:00
emulators Files available on ftp.netbsd.org now. 2003-01-23 14:32:57 +00:00
finance Fix build after the guile 1.4/1.6 split by properly using the pkgsrc 2003-01-24 04:28:52 +00:00
fonts Add INTERACTIVE_STAGE=fetch, since this package has a _FETCH_MESSAGE. 2003-01-24 15:38:42 +00:00
games Dynamically add -lpth only if PTHREAD_TYPE is "pth". 2003-01-25 12:09:11 +00:00
graphics Add a buildlink2.mk file for use by other package Makefiles. 2003-01-25 12:06:27 +00:00
ham USE_PKGLOCALEDIR. 2002-12-01 14:37:12 +00:00
inputmethod Use "mk/pthread.buildlink2.mk" instead of "devel/pth/buildlink2.mk" to 2003-01-19 08:48:47 +00:00
lang Note in USE_NCURSES variable which functions actually are missing for this 2003-01-24 13:36:17 +00:00
licenses Add adobe acrobat reader license, from 2003-01-17 12:15:39 +00:00
mail Updated postfix to 2.0.3 2003-01-25 07:22:19 +00:00
math Bump revision; installed location change. 2003-01-25 05:27:27 +00:00
mbone s/INSTALL_*/BSD_INSTALL_*/ in patch-ad, remove unnecessary MAKE_ENV. 2003-01-19 07:13:49 +00:00
meta-pkgs Fix typo: >= instead of > for pan dependency 2003-01-17 02:30:45 +00:00
misc Note in USE_NCURSES variable which functions actually are missing for this 2003-01-24 13:36:17 +00:00
mk Create a fake libpthread.la that corresponds to /usr/lib/libpthread.*. 2003-01-25 08:39:54 +00:00
net Note in USE_NCURSES variable which functions actually are missing for this 2003-01-24 13:36:17 +00:00
news USE_PKGLOCALEDIR=yes 2003-01-10 07:39:46 +00:00
packages Add .cvsignore to stop cvs update listing every distfile and more 1999-11-24 11:53:24 +00:00
parallel The lib/pkgconfig has been added to the list of standard directories, so do 2003-01-02 22:44:43 +00:00
pkgtools Update to 3.45: 2003-01-24 15:16:31 +00:00
print Accomplish the same thing as patch-ab, enabling the output buffer, without 2003-01-25 09:37:38 +00:00
security Remove (hi hubert!) 2003-01-25 13:59:05 +00:00
shells s/INSTALL_SCRIPT/BSD_INSTALL_SCRIPT/ in patch-aa, remove unnecessary MAKE_ENV. 2003-01-19 09:12:06 +00:00
sysutils No reason to conflict with mkisofs, pointed out by Manuel Bouyer. 2003-01-25 10:10:06 +00:00
templates Fix the location of DESCR for the readme files 2001-11-03 03:26:08 +00:00
textproc - Enable termcap. Chack tputs() after -ltermcap is detected (configure*). 2003-01-24 14:12:03 +00:00
time - s/INSTALL_*/BSD_INSTALL_*/ in patch-aa, remove unnecessary MAKE_ENV. 2003-01-19 10:27:56 +00:00
wm don't make the assumption we are using gcc and pass -Wall. 2003-01-23 01:32:56 +00:00
www Sort. 2003-01-25 05:32:45 +00:00
x11 Note that qt3 requires C++. 2003-01-25 13:21:04 +00:00
Makefile Switch the top level pkgsrc 'readme' and 'cdrom-readme' targets to use the 2003-01-05 13:37:15 +00:00
Packages.txt add missing dot 2003-01-22 19:22:05 +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

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