Automatic conversion of the NetBSD pkgsrc CVS module, use with care
4953cd65af
Based on a PR pkg/20825 by Hiramatsu Yoshifumi, modified by me. - follow PKG_SYSCONFDIR List of major changes for this release: * Regular Expressions Phase 1 ICU 2.4 introduces a Regular Expression C++ API that is modeled after the JDK 1.4 API. ICU 2.4's Regular Expression API supports Unicode level 1 regular expressions (see Unicode Regular Expression Guidelines) but not all pattern metacharacters and features are supported yet. Regular expressions leverage all of the UnicodeSet support, including all Unicode 3.2 property names and property value names. Future ICU releases will complete the pattern support, add support for higher Unicode regex levels, and improve performance. For more details see the API References and the User Guide. * Modularized ICU library building ICU 2.4 provides build-time switches to prune parts of the library code, for smaller custom distributions. For details see the readme file. * Character set alias management support Additional APIs map alias+standard to a unique charset name (e.g., "Shift-JIS"+"IANA"->"ibm-943_P14A-2000") and enumerate all charset names in the alias table, not just the installed ones. See convrtrs.txt and ucnv.h. These APIs allow programmers to avoid data corruption problems when different platforms use the same names for different character conversion mappings. * EBCDIC-z/OS converter option The EBCDIC converter now handles swapped LF/NL mappings algorithmically instead of with modified .ucm/.cnv conversion table files. This makes this behavior available for all supported EBCDIC conversions without adding to the data package size. See "swaplfnl" in convrtrs.txt. * Additional converter A new converter implementation has been added for the encoding of IMAP mailbox names. See RFC 2060/5.1.3. Mailbox International Naming Convention and "IMAP-mailbox-name" in convrtrs.txt. * Customizable break iteration ICU 2.4 allows registration of a BreakIterator with a locale ID. This allows applications to provide more sophisticated word/sentence break engines and use them seamlessly with the ICU APIs. In future releases, this registration mechanism will be extended to all relevant ICU services. If you are interested in ICU customization, please try out this feature. * Collation performance ICU 2.4 collation was improved in several areas, with an emphasis on performance: * Latin-1: Improved performance of u_strcoll(). * Russian/Cyrillic: Improved performance by tailoring collation for cyrillic-script languages, removing UCA contractions that are not used for modern Russian (this uses the [suppressContractions] tailoring option). * Korean: Improved performance by resolving collation elements for modern Hangul syllables at build time (this uses the [optimize] tailoring option). * Japanese: The default strength for Japanese was reduced from quaternary to tertiary as in all other locales. * UnicodeSet performance UnicodeSet performance is significantly improved, especially for add(codePoint) and contains(codePoint). * Unicode property aliases ICU 2.4 introduces APIs for mapping between all appropriate Unicode property aliases and property value aliases and ICU property enumeration constants. See u_getPropertyName() etc. in uchar.h. * Unicode string functions * There are new C functions for searching for last occurrences of characters and partial strings. See u_strrstr(), u_strrchr32() etc. * New C/C++/Java functions for efficient checking if a string contains more than a certain number of code points. See hasMoreChar32Than(). * Copying UnicodeStrings via the standard assignment operator and copy constructor does not preserve readonly aliasing any more because this can sometimes have unexpected and dangerous effects. A new fastCopyFrom() member function provides the old copy semantics. See Jitterbug 1794 for more details. * UTF macros simplified The low-level C macros for handling code points in 8-bit and 16-bit Unicode strings have been replaced by a simpler, more consistent set with more concise names. For details see utf_old.h and utf.h. Similarly, ICU 2.4 defines the UChar32 consistently (now always as int32_t) and adds a U_SENTINEL non-code point value for new APIs. * Performance tests ICU 2.4 has a new performance test framework and additional performance tests using this framework. This is not currently documented, but it is available as part of the source distribution at source/test/perf/. |
||
---|---|---|
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.