Automatic conversion of the NetBSD pkgsrc CVS module, use with care
Find a file
2001-07-22 20:54:31 +00:00
archivers Mechanical changes to buildlink.mk files to use EVAL_PREFIX to set 2001-07-20 01:54:31 +00:00
audio Complete buildlinkization. 2001-07-22 16:54:22 +00:00
benchmarks Remove empty trailing line. 2001-07-18 10:31:20 +00:00
biology Update to 5.0. 2001-07-08 13:36:33 +00:00
cad update to libgeda-20010708 2001-07-17 03:06:27 +00:00
chat Convert to use buildlink.mk files and mark as USE_BUILDLINK_ONLY. 2001-07-15 12:22:16 +00:00
comms Mechanical changes to buildlink.mk files to use EVAL_PREFIX to set 2001-07-20 01:54:31 +00:00
converters Fix build problems caused by buildlink conversions. This error code have 2001-07-22 13:26:46 +00:00
cross update for zoularis-20010704 2001-07-04 21:05:03 +00:00
databases - Install document and examples. 2001-07-22 15:52:10 +00:00
devel Remove a shared library that doesn't seem to get built. Noted missing in 2001-07-22 16:27:51 +00:00
distfiles These files belong to $MASTER_SITE_LOCAL - moved them there! 2000-12-05 00:23:05 +00:00
editors Added and enabled yudit, a unicode editor 2001-07-15 16:47:09 +00:00
emulators Add -Wl,-R for X11 libraries. Noted missing in recent bulk build. 2001-07-22 16:25:10 +00:00
finance Convert to use buildlink.mk files and mark as USE_BUILDLINK_ONLY. 2001-07-02 21:54:19 +00:00
fonts add ko-*. supersedes ksc5601fonts. 2001-07-22 01:13:10 +00:00
games Update this pkg to 1.0.0, the current version of crossfire. No changelog 2001-07-19 05:58:51 +00:00
graphics add and enable eog 2001-07-22 01:41:32 +00:00
ham Add an info dir entry to tntdoc.info and fix Makefile and PLIST accordingly. 2001-05-16 22:07:02 +00:00
japanese Mechanical changes to buildlink.mk files to use EVAL_PREFIX to set 2001-07-20 01:54:31 +00:00
lang Mechanical changes to buildlink.mk files to use EVAL_PREFIX to set 2001-07-20 01:54:31 +00:00
licenses VMWare license in preparation for the package in emulators/vmware. 2001-07-07 14:24:21 +00:00
mail Add & enable mailcrypt 2001-07-22 20:54:31 +00:00
math Fix rpath lossage noted in recent bulk build. 2001-07-22 16:45:46 +00:00
mbone CPPFLAGS is now passed to MAKE_ENV and CONFIGURE_ENV by bsd.pkg.mk, so 2001-06-11 06:34:17 +00:00
meta-pkgs Update to new COMMENT style: COMMENT var in Makefile instead of pkg/COMMENT. 2001-02-17 17:52:59 +00:00
misc Swap patch-ab and patch-ac so that configure.in gets touched before configure. 2001-07-22 16:34:44 +00:00
mk don't try and do 'mount -o async -u /usr' because we don't know that the user 2001-07-21 19:58:32 +00:00
net Remove distclean target that made trouble, as noted in recent bulk build. 2001-07-22 16:52:30 +00:00
news Add "--enable-setgid-inews" to "CONFIGURE_ARGS" because "inews" is 2001-07-16 13:41:18 +00:00
packages Add .cvsignore to stop cvs update listing every distfile and more 1999-11-24 11:53:24 +00:00
parallel forgot to cvs add these first. 2001-05-24 19:51:47 +00:00
pkgtools 'file' should be replaced by '${FILE_CMD}' now. 2001-07-15 12:56:58 +00:00
print Don't install .elc files, no matter if emacs is installed or not. 2001-07-22 17:18:04 +00:00
security Update ruby-ssl to 0.3.1c. 2001-07-22 12:36:09 +00:00
shells Add a patch from Rafal Boni <rafal@mediaone.net> to recognize mipseb 2001-06-20 05:39:02 +00:00
sysutils Make it work with latest windowmaker libraries. Buildlinkify a bit. 2001-07-22 17:42:08 +00:00
templates Note how to report problems, or send updates or suggestions. 2001-03-19 17:44:30 +00:00
textproc Add and enable p5-XML-Grove 2001-07-20 07:53:43 +00:00
time Mark as NO_SRC_ON_FTP as these are now fetched from MASTER_SITE_LOCAL. 2001-07-16 10:41:18 +00:00
wm Mechanical changes to buildlink.mk files to use EVAL_PREFIX to set 2001-07-20 01:54:51 +00:00
www "www.analog.cx" is still down, use "http://www.web42.com/analog/" as 2001-07-22 08:12:45 +00:00
x11 Mechanical changes to buildlink.mk files to use EVAL_PREFIX to set 2001-07-20 01:54:51 +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 Make the example buildlink.mk file more complete by showing how 2001-07-20 02:00:47 +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 add two 2001-07-21 14:01:30 +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.