Update to 20020213.

pkgdb(1):
- Set the default answer to no when a score is under 80%.

pkgdb(1), portupgrade(1):
- Add a BUGS entry to each of the two man pages to note that a user
  must run pkgdb -fu to rebuild a corrupt pkgdb.

pkgdb(3):
- Add a silly workaround against a possible bug of the dbm module to
  keep a pkgdb from getting insane and rebuilt.

- [exp.] Add a knob environment variable PKG_DBDRIVER to specify an
  alternative binary database format for pkgdb.  The available options
  are:

    "bdb_btree":
        DB 3.x/4.x B+tree; requires databases/ruby-bdb.

    "bdb_hash" or just "bdb":
        DB 3.x/4.x hash; requires databases/ruby-bdb.

    "bdb1_btree" or just "btree":
        DB 1.85 B+tree; requires databases/ruby-bdb1.

    "bdb1_hash", or just "bdb1" or "hash":
        DB 1.85 hash; requires databases/ruby-bdb1.  This should be
        equivalent to the default except some tuning parameters, but
        it is quite possible that ruby-bdb1 is stabler than the
        standard dbm module included in ruby.

    default:
        DB 1.85 hash; uses ruby's standard dbm module.

  In principle, a B+tree database is faster to store data, a little
  bit slower to extract data, and takes more space than a hash
  database.

  This is still an experimental/undocumented feature only for those
  interested, although I don't believe it brings any unstability.
  Note that you can always run pkgdb -fu to rebuild a database.

portcvsweb(1):
- Invoke browsers with system() instead of exec() so that it will
  properly try every browser in turn - exec('/bin/sh', '-c', '..') may
  cause an error within /bin/sh but it never returns.

  Reported by:	Jimmy Olgeni <olgeni@FreeBSD.org>

portsclean(1):
- Make portsclean -D remove empty directories (recursively) as well.

0 files changed, 0 insertions, 0 deletions