portupgrade:
Fix a couple of bugs where `portupgrade -h | more' doesn't show the
usage nicely.
Reported by: Gregory Neil Shapiro <gshapiro@gshapiro.net>
portsclean:
Make good use of portsdb and pkgdb, use lazy (but virtually
sufficient) checks and get distclean much faster. (both -D and -DD)
portsdb:
Do not fail even if some categories are missing in the ports tree.
Reported and tested by: Jos Backus <josb@cncdsl.com>
And some other internal bugfixes that do not affect the user tools.
release again. (Hopefully)
portupgrade:
Delete an unneeded exception snatcher. This fixes a bug where ports
marked as IGNORE are not properly skipped.
pkgdb:
Rebuild pkgdb if it looks like broken, instead of resulting in
failure.
Unbreak regexp match. ;)
Fix a typo of a variable name in an error message.
[Reported by: Stijn Hoop <stijn@win.tue.nl>]
portsdb:
Allow a port dir to be a symlink to a directory.
Add support for the case where some catetories are missing in a
ports tree.
[Submitted by: Jos Backus <josb@cncdsl.com>]
pkgdb:
Fix a type error and unbreak date-based pkg glob.
[Reported by: Ollivier Robert <roberto@keltia.freenix.fr>]
portupgrade:
Silence pkg_info when it does not find a package.
[Submitted by: Jimmy Olgeni <olgeni@uli.it>]
pkgdb:
Make pkgdb fixer's dependency guesser aware of language specific
categories. Now it suggests ja-qt-2.3.1 instead of qt-1.45_1 for
a missing qt-2.3.1.
Do not fail over a package entry that has no +COMMENT file, like an
XFree86 package entry faked by the FreeBSD installer.
[Reported by: Ollivier Robert <roberto@eurocontrol.fr>]
portsdb:
Do not allow specifying a ports glob using a relative path to the
current directory. This prevents the tools from confusing when the
current directory is under PORTS_DIR.
Give a better progress display.
many bugfixes. Check out http://www.exploits.org/nut/release/new-0.45.1.txt
for more details. Highlights include experimental USB support, and the
various programs dropping more privileges after startup.
* Clean up the Makefile a little by grouping more of the CGI-dependent
stuff together. Improve the pkg-plist in this regard as well. Make a
directory and install a conf file sample that the software Makefile's
are missing for some reason.
* Make the cgi directory depend on one of the previously
discussed plans to use PREFIX/www/cgi-bin if it exists already, and
PREFIX/share/apache if not.
create a new database for the very first time. (Run "pkgdb -fu" if you have
20011006 installed)
Fix MAN1 entries.
Remove old database pkgdb.byfile.db on installation.
(new database is named pkgdb.db)
Beware, there can probably be some bugs left in the new pkgdb code.
In such a case please run "pkgdb -fu" to fix the situation.
overall:
Utilize pkgdb better and optimize.
portupgrade:
Do not scan packages all at once when -P is given, but find one per
request. [Requested by: Hideaki OKADA <hokada@isl.melco.co.jp>]
Create a backup package record in tmpdir instead of pkgdbdir, in
order not to update pkgdbdir's mtime.
Rephrase/add messages.
portinstall:
Commit major changes and improvements over portinstall.
Now it warns and asks the user for confirmation if a port is being
installed when a package of the same origin is already installed.
Upgrade all the required packages before installing a new port.
[Requested by: Hajimu UMEMOTO <ume@mahoroba.org>]
Do not install ports immediately but queue them up, then install
them after upgrading all the specified and required packages.
pkgdb:
Record pkgname <=> origin mapping in the pkgdb and make full use of
it instead of repeatedly calling pkg_info -o which has undesirable
overheads.
Make portupgrade, pkg_deinstall update the pkgdb after they
install/deinstall packages or modify package records.
Integrate pkgdepfix(1) within. (pkgdb -F/--fix)
Add -o/--origin, which looks up an origin of a package in pkgdb.
Detect added/deleted/reinstalled packages more strictly so pkgdb can
keep being sane and consistent.
Do not fail over a small conflict found during updating pkgdb;
portupgrade should not be aborted by such a minor problem.
pkgdepfix:
Obsolete -o and turn -o on by default. Now we can look up an origin
of a package so quickly thanks to the pkgdb.
Integrate into pkgdb(1). (pkgdb -F/--fix)
portsdb:
A date spec is not a valid ports glob; emit a warning if specified.
[Found by: Hajimu UMEMOTO <ume@mahoroba.org>]
and that on www.idaemons.org didn't match. They are identical in the
uncompressed form but I think I compressed one with -9 and another
with -6 somehow. Thereby list the MD5 checksums of both in pkg-plist
as a workaround.
The one on ftp.FreeBSD.org will be overwritten by the one on
www.idaemons.org soon.
Submitted by: John Merryweather Cooper <john_m_cooper@yahoo.com>
Correct format arguments for unsigned long longs;
In printf, use %llu
In sscanf, use %qu
These were both previously using %Ld...
This fixes generation of DVDs >4Gb in size.
overall:
- Implement new package glob patterns: {<|<=|>=|>}{date|pkgname_glob}.
For example, you can rebuild and reinstall all the dependent
packages of png that had been installed prior to png this way:
portupgrade -fr png -x '>=png'
- Introduce the packages database, which is currently a simple hash
that maps file paths to package names.
Inspired by: NetBSD
pkgdb(1): (new)
- A command to create/update the packages database.
pkg_which(1): (new)
- A command to check which package a file came from quickly.
portsclean(1):
- Suppress "can't cd" error messages.
Submitted by: Jos Backus <josb@cncdsl.com>
ports_glob(1): (new)
- Give portsdb(1)'s ports glob expanding feature a suitable name.
overall:
- Work around pkg_info(1)'s "feature" where it gets info from
package files under the packages directory prior to installed
packages.
[Reported by: kuwa@flab.fujitsu.co.jp]
portupgrade:
- Skip ports that are marked as IGNORE.
[Requested by: Jimmy Olgeni <olgeni@uli.it>]
portsdb:
- Stop specifying -j# when making a ports index to avoid outputting
a buggy INDEX.
portsclean:
- Do not assume a distinfo file is in each port's own directory, and
use `make -V MD5_FILE', in order to support master-slave ports
properly.
Now that RUBY_ARCH has been changed not to include a minor version of
the system, you no longer need to have ruby_s in order to cope with
the migration problem with a minor system upgrade like 4.3 -> 4.4.
You will need ruby_static only if you are going to do a major upgrade
of your system like 4.3 -> 5.0.