* Change a legacy part of code for gathering dependecies. It fixes
situation when some depends ports could be updated even when it
was up-to-date. As a result I added another check for -R option.
* Fix a wrong condition in portsclean. Now -L option works again.
* Change a semantic for -q option. Now it means 'quiet'. Don't
show a message when -N specified and there is an already installed
package. (Made for DesktopBSD).
Reported by: pav, Peter Hofer (DesktopBSD)
- Just ignore a package if there is no port directory exists. A correct way
for users is to place the ports in HOLD_PKGS in pkgtools,conf, but
they did not. So it makes my life a little easy.
* Many bugs fixed (thanks to all reporters).
* Semantic for -c and -C has changed. -c runs 'make config-conditional'
and -C 'make config' (forced config).
* All ports now runs under portupgrade/portinstall control.
with system ones. portsclean -Li ask to remove them. No removes by
default, but we don't want an user remove system libraries just press 'y'
in portscleanup -Li.
PR: ports/116830
Reported by: clemens fischer <ino-news at spotteswoode.dnsalias.org>
An unpleasant bug was fixed when pkgdb could accidently remove some
dependencies in +CONTENTS files. It's recomented to run pkgdb -L once
after upgrade to fix dependencies list. See UPDATING file.
Reported and tested by: Randy Pratt <bsd-unix_AT_earthlink.net>
Most visible changes are:
* Database files locking. Only one process can write to them
in the same time.
* pkgdb -F is more smart now and takes OPTIONS, make.conf and
pkgtools.conf settings into account.
Moreover:
* Many bugs fixed.
* Many code refactored.
It's exactly like 2.1.3 but without summary messages and
fixed bug when BDB4 was defined but tried only bdb1 driver and
fall back to dbd driver.
- Add an option WITH_BDB1. Both BDB1 and BDB4 options can be off.
Ruby dbd driver will use in the case.
- Update to 2.1.0
o rewrite version checking. Now it's compliant with pkg_version(1) algorythm
o fix shebangs in test/*
o add test in test_pkgversion.rb from test-pkg_version.sh
o fix test_pkgdb.rb
o fix pointyhat URL in pkgtools.conf and pkgtools.rb
o make comparisons when updates from packages. It compared package names
instead versions. It gives a weird results when port was renamed
(eg. mozilla-firebird -> firefox) [1]
o don't show a warning about origin changing when origins are the same. [2]
It rids us from messages like:
Package origin of 'pan' has been changed: 'news/pan' -> 'news/pan'
PR: ports/62990 [1], ports/98153 [2]
Submitted by: Leland Wang <llwang at infor.org> [1]
tobez [2]
Approved by: maintainer (silence for a month, no activity seen for 4 monthes)
daichi (blessed)
ports (silence)
a number open PRs from 2003 year
Inspired by: az
* portversion(1) also reads MOVED and trace origin change,
and, when invoked with "-v", displays the new origin.
Example:
% portversion -v screen
screen-4.0.2_2 < needs updating (port has 4.0.2_3) (=> 'sysutils/screen')
* Add "--ignore-moved" to portupgrade(1) and portversion(1).
When invoked with this option, both programs totally ignore MOVED.
If you encounter strange behaviour of these programs, try this out.
* Add IGNORE_MOVED option to pkgtools.conf.
This can be used to selectively ignore MOVED by pkgs.
See pkgtools.conf.sample for details.
* Keep the order of MOVED entries, and do not trace back to old entries.
Previously, when encounters the following entries,
editors/emacs|editors/emacs19|2004-03-20|emacs 19.x moved to a non-default port location
editors/emacs21|editors/emacs|2004-03-20|emacs 21.x moved to default port location
portupgrade traces as "editors/emacs21" -> "editors/emacs" -> "editors/emacs19".
I thought this behavior should not be what we want to, so added this change.
PR: ports/91272
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org> (maintainer)
Thank you for reporting. I also discovered this problem a few hours ago.
The source of this trouble is that the following line exists in MOVED,
lang/php4|lang/php4|2003-05-22|re-separated from www/mod_php4
where "moved from" and "moved to" is the same, but portupgrade
does not check this case and infinite loop occurs.
Fix to this problem will be in the next portupgrade release,
but in the meanwhile, whould you commit the following patch,
please?
PR: ports/91209
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org>
(1) For years, I have experienced that portupgrade sometimes
runs very slow. After some investigation, I found that
"pkgdb -aF" is invoked from portupgrade or other programs
(such as portversion) without having sufficient privilege
to modify /var/db/pkg/, and that error is not caught by the
caller program, and "pkgdb -aF" is invoked repeatedlly.
So, I fixed the following things:
- When pkgdb internally invoked from other program exits
with error, make the caller program also exit with error.
- Display the error messages of pkgdb that run internally
from other program.
When portupgrade or other programs die with the following error,
** You do not own /var/db/pkg. (use -f to force or run as root)
Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ
please run "pkgdb -aF" as the user that owns /var/db/pkg (usually root).
(2) Make new tarball that contains the above fix and all
patches in files/. Bump PORTVERSION to 20051204 and change
MASTER_SITES.
PR: ports/89917
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org>
fix minor documentation issues with the portsclean(1) manpage.
1. In the SYNOPSIS, the -L option is excluded.
2. In the description for the -Q option, an example of the -QQ option
is not given and since the other descriptions do this,
it looks nicer and is easier to read.
PR: ports/82666
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org> (maintainer)
Pointed out by: Jason E. Hale <jhale@bluebottle.com>
every run, which also makes portversion(1) works for non-root users
again. This is done by simply having the flag file in /var/db/
(thanks to pav for the suggestion).
- While here anyway, fix some make warnings during install on FreeBSD 6.
PR: ports/81088
Reported by: many
Tested by: Yoshiaki Kasahara <kasahara@nc.kyushu-u.ac.jp>
Approved by: erwin (mentor)
portsdb(1):
- Add a -F flag, which calls make fetchindex internally to
update the ports index file.
portupgrade(1):
- Make -fP properly reinstall an installed package using a binary
package.
- Do not use a binary package when custom MAKE_ARGS or -m option is
defined, unless -PP is specified.
portsclean(1):
- -L: Make sure that a library does not shadow itself.
misc.:
- RcNG'ify the startup script.
- Do not use Object#class which is obsolete in Ruby >=1.8.
