Automatic conversion of the NetBSD pkgsrc CVS module, use with care
Find a file
2001-10-25 18:52:04 +00:00
archivers Use ${MASTER_SITE_PERL_CPAN:=xx/} and not ${MASTER_SITE_PERL_CPAN:=xx} 2001-10-23 19:27:31 +00:00
audio Having a 3-line script for the pre-configure stage is overkill - move 2001-10-25 17:26:01 +00:00
benchmarks bump version to 1.0nb1 - the bw_pipe pipe descriptor fix 2001-09-22 20:48:28 +00:00
biology Deprecate NO_WRKSUBDIR, replacing it with an explicit assignment of: 2001-09-09 20:36:07 +00:00
cad I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
chat I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
comms I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
converters I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
cross Sync with PEACE repositry. 2001-10-21 12:24:15 +00:00
databases Update for OpenLDAP-2.0.x. 2001-10-25 18:52:04 +00:00
devel Note package is strongly-buildlinked (trivially). 2001-10-25 15:42:56 +00:00
distfiles These files belong to $MASTER_SITE_LOCAL - moved them there! 2000-12-05 00:23:05 +00:00
editors plug string format vulnerability. 2001-10-25 07:46:27 +00:00
emulators I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
finance Get guile-slib dependency from g-wrap. 2001-10-03 09:02:44 +00:00
fonts Update SHA1 sum of jiskan16-2000-1.bdf.gz and jiskan16-2000-2.bdf.gz. 2001-10-25 16:47:29 +00:00
games Note addition of games/sjeng. 2001-10-25 04:44:43 +00:00
graphics I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
ham Updated to tfkiss-1.2.4: 2001-09-09 08:16:22 +00:00
japanese - Create explicitly ${PERL5_SITELIB}. 2001-10-25 14:43:22 +00:00
lang Update the tcl-expect packages to be based on expect-5.33. 2001-10-24 23:40:02 +00:00
licenses VMWare license in preparation for the package in emulators/vmware. 2001-07-07 14:24:21 +00:00
mail I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
math I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
mbone Deprecate NO_WRKSUBDIR, replacing it with an explicit assignment of: 2001-09-09 20:36:07 +00:00
meta-pkgs jadetex was renamed to tex-jadetex 2001-10-04 18:50:29 +00:00
misc only conflict on rpm2cpio < 1.0nb1 2001-10-24 00:26:51 +00:00
mk Sort "PATCH_SITES" using "MASTER_SORT" and "MASTER_SORT_REGEX", too. 2001-10-25 18:12:53 +00:00
net Do the whole automake step, not just the autoconf step, at pre-configure 2001-10-25 16:13:06 +00:00
news I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
packages Add .cvsignore to stop cvs update listing every distfile and more 1999-11-24 11:53:24 +00:00
parallel Mechanical changes to 375 files to change dependency patterns of the form 2001-09-27 23:17:41 +00:00
pkgtools Upgrade to version 0.51 of bsdpak. From Ben Collver in PR 14257. 2001-10-16 09:17:08 +00:00
print I can be the new MAINTAINER for lyx (suggested by frueauf) 2001-10-25 14:18:23 +00:00
security Update pgpdump to 0.13 2001-10-25 17:47:25 +00:00
shells Don't compress the manual pages of this package because "zshall.1" tries 2001-10-05 16:36:00 +00:00
sysutils I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
templates Note how to report problems, or send updates or suggestions. 2001-03-19 17:44:30 +00:00
textproc Back out last commit. Under certain circumstance (which??) the files 2001-10-24 14:36:14 +00:00
time I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
wm I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
www Pass ${command_args} in stop_cmd, as requested in pkg/14349. 2001-10-25 10:20:59 +00:00
x11 Move a one-line configure script to be a patch, and update information 2001-10-25 17:39:10 +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 I am a triple idiot. The only relevant variable that x11.buildlink.mk 2001-10-24 22:10:43 +00:00
pkglocate Update the usage message to explain what each option letter does. 2001-04-03 09:28:32 +00:00
README update a bit 2001-06-06 19:41:05 +00:00
TODO Remove an out-of-date update entry, and add a note about resin (it can't be 2001-10-25 17:56:10 +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.