Automatic conversion of the NetBSD pkgsrc CVS module, use with care
39c70fc4a8
Fixes another security hole...
Full list of changes:
* Configuration flexibility
+ pine configurations can now be stored remotely on an imap
server for access from different locations without the need
to configure for each location.
+ configuration may be split into two parts: generic
configuration and exceptional, per-platform configuration.
+ signatures can now be stored remotely or as part of the
pinerc file
+ for configuration options which are lists, inheritance is
supported
* New security features
+ SSL support for Unix Pine (source code only)
+ SSL enhancements for PC-Pine
* Minor rule enhancements
+ status of a message (New, Deleted, etc.) can now be used as
criteria for pattern matching.
+ "move-only-if-not-deleted" option in filtering to lessen the
chance of messages being filtered more than once when running
multiple pine sessions.
+ ability to set arbitrary headers in roles.
+ news filtering made more efficient.
* Basic threaded sorting (Expanded functionality to be added in a
future version).
* Enhanced MAPI support for PC-Pine
* Various other new features and configuration options
+ alternate-compose-menu
+ by-replyto for saved-msg-name-rule
+ check-newmail-when-quitting
+ continue-tab-without-confirm
+ expose-hidden-config
+ expunge-only-manually
+ incoming-startup-rule additions
+ literal-signature
+ mark-for-cc
+ prefer-plain-text
+ pruning-rule, for monthly sent-mail renaming and deleting
+ quell-extra-post-prompt
+ hidden feature allow-changing-from defaults to on
* New command line options:
+ -p , pinerc can now refer to a remote mailbox which
contains the configuration file
+ -x , is how you override your default
pinerc settings with exceptions for a particular platform,
may be local or remote
+ -aux , allows you to tell
Pine the local directory to use for auxiliary files when
pinerc is remote (PC-Pine only)
+ -copy_pinerc and -copy_abook options
+ -v option
Bugs that have been addressed in this release include:
* Incoming mail with an extremely long From address can cause a
buffer overflow on the stack (security)
* X-Keywords crash for unix formatted mailboxes
* Composer word wrapping needlessly wraps words
* New messages appear in zoomed view
* "Bad msgno 0" filtering crash
* "+" during login doesn't always mean that SSL is being used
* news filtering refilters messages that had already been filtered
* Goto and Save can't access folders that are readable but not
listable
* Goto doesn't allow access of folders outside of a Collection List
* PC-Pine SSL functionality broken in Windows 2000/Millennium
* FromOrTo and To in index-format don't work for newsgroups
* Sorting by score doesn't always work
* Viewing of very large messages uses more memory than is need
* Loss of body for reply to multipart/signed mime messages
* Pine crashes when replying to or forwarding messages with certain
types of attachments
* Brackets are falsely recognized as url characters
* Crash when enclosing options in quotes for PC-Pine
* Newsgroup posting doesn't allow posting to additional news servers
|
||
|---|---|---|
| archivers | ||
| audio | ||
| benchmarks | ||
| biology | ||
| cad | ||
| comms | ||
| converters | ||
| cross | ||
| databases | ||
| devel | ||
| distfiles | ||
| editors | ||
| emulators | ||
| fonts | ||
| games | ||
| graphics | ||
| ham | ||
| japanese | ||
| lang | ||
| math | ||
| mbone | ||
| meta-pkgs | ||
| misc | ||
| mk | ||
| net | ||
| news | ||
| packages | ||
| parallel | ||
| pkgtools | ||
| plan9 | ||
| security | ||
| shells | ||
| sysutils | ||
| templates | ||
| textproc | ||
| www | ||
| x11 | ||
| Makefile | ||
| Packages.txt | ||
| pkglocate | ||
| README | ||
$NetBSD: README,v 1.11 2000/07/23 18:02:33 fredb 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 where you found this README, or in your top-level pkgsrc directory.