Automatic conversion of the NetBSD pkgsrc CVS module, use with care
Changes include: * New try/catch mechanism for control of exception handling. * Fixed memory leaks in solve and svd. * Builtin `tril' and `triu' functions -- sparse arrays stay sparse. * Fixed integer overflow problems in `band' and `cram'. * Incorporated the SuperLU package for solving sparse linear systems. Previously, sparse systems were converted to dense and solved with LAPACK (unless configured with BCSLIB-EXT). * Included support for memory allocation debugging with dmalloc. * Improved the logical operations to do a much better job at maintaining sparsity. * New standard function `select'. * Changes to the matrix bandwidth minimization code. The old `band' function is now called `gpskca' and can do either profile or bandwidth minimization of symmetric or hermitian matrices. Matrix statistics are computed by the new `band' function. * New standard functions `linspace' and `logspace'. * New standard function `equilibrate' computes scale factors to improve the condition of a matrix. However, sparse code has not yet been included. * Fixed several deficiencies in the `transform' function. * Removed old get_ascii and put_ascii functions. I doubt if anyone has used these in the last decade. To read and write matrices in text files, use the algae MatrixMarket package. * Fixed several errors with hermitian symmetry. * Fixed mishandling of sparse matrix multiplication case where non-zero factors give a zero result. * Added "short-circuit" logical operators && and ||. * Added the `cram' builtin function -- it's the same as `form' except the output array is sparse when that makes sense. * Added the `product' user function -- product of array elements. * Added `mksparse' and `exsparse' functions for converting matrices to and from coordinate form. * Switched to LAPACK's DGGEV now that DGEGV is deprecated. Also use the new workspace size query feature in LAPACK, rather than working it out ourselves. * Use LAPACK's ZHEGV and ZGGEV for complex generalized eigenvalue problems. * Use floating point exception support from glibc 2.2 on Linux. * Improved accuracy and behavior for complex arguments in functions `log', `asin', and `acos'. * Added inverse hyperbolic trig functions `asinh', `acosh', and `atanh'. * Various minor bug fixes. |
||
---|---|---|
archivers | ||
audio | ||
benchmarks | ||
biology | ||
cad | ||
chat | ||
comms | ||
converters | ||
cross | ||
databases | ||
devel | ||
distfiles | ||
doc | ||
editors | ||
emulators | ||
finance | ||
fonts | ||
games | ||
graphics | ||
ham | ||
inputmethod | ||
lang | ||
licenses | ||
math | ||
mbone | ||
meta-pkgs | ||
misc | ||
mk | ||
net | ||
news | ||
packages | ||
parallel | ||
pkgtools | ||
security | ||
shells | ||
sysutils | ||
templates | ||
textproc | ||
time | ||
wm | ||
www | ||
x11 | ||
Makefile | ||
Packages.txt | ||
pkglocate | ||
README |
$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.