psearch is an utility for searching the FreeBSD Ports Collection.
It allows you to use regular expressions, and has support for searching
the long description (pkg-descr files), as well as inverse matches that
allow filtering of ports.
WWW: http://www.maxlor.com/freebsd-scripts.shtml
PR: ports/93490
Submitted by: Benjamin Lutz <benlutz@datacomm.ch>
* Add a check for .mo (translation) files, and warn if USE_GETTEXT is not
set. [1]
* Make sure USE_RC_SUBR checking does macro expansion to catch cases were
USE_RC_SUBR=${PORTNAME} (for example). [2]
PR: 93273 [2]
Requested by: kris [1]
* Add a check to see if PORTREVISION=0 in master ports. [1]
* Add checks for direct use of the pkg_* commands. [2]
* Add a check that if a port is new, it is not maintained by
ports@FreeBSD.org. [3]
* Do not warn about .la files if USE_KDELIBS_VER is set. [4]
* Add a check for deprecated use of USE_RC_SUBR along with checks for its
proper use. [5]
PR: 91324 [1]
92888 [2]
92665 [3]
92586 [4]
Submitted by: lofi [4]
dougb [5]
* update from 2.2.1 to 2.3.0
* fix options parsing so `make' in a pristine directory works
as expected [1]
* sort the new plist
PR: ports/92881
Submitted by: Vasil Dimov <vd@FreeBSD.org>
Portsearch allows searching for ports that install some file, like
``find /usr/ports -name pkg-plist |xargs grep pattern''
but honoring PLIST_(FILES|DIRS) and %%FOOBAR%% variables.
Approved by: garga (mentor)
src tree.
This only affects users of FreeBSD 5.4 and earlier, since the port is
IGNOREd for recent versions of the FreeBSD base system.
PR: ports/92563
Approved by: linimon
This version contains fix to prevent cache-init crashing when it tries
to process the currently empty net-p2p port category.
PR: ports/92503
Submitted by: Matthew Seaman (maintainer)
* Update quoting requirements for new bsd.port.mk
* Warn on use of USE_REINPLACE [1]
* Recommend @dirrmtry instead of @unexec rmdir [1]
Requested by: pav [1]
misc/tinderbox does not install the php extension for the
selected database, because the extension is added to USE_PHP
after bsd.port.pre.mk inclusion.
PR: ports/92065
Submitted by: Vasil Dimov <vd@FreeBSD.bg>
* 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) Change the versioning scheme of portupgrade.
portupgrade now becomes 2.0.0!
(2) Add FreshPorts support to portcvsweb(1).
You can view CVS history via FreshPorts instead of CVSweb
by using "portcvsweb -F". See the man page of portcvsweb(1) for details.
(3) If the change of the origin is written in MOVED,
portupgrade reads and chases it.
You no longer need to supply the origin of the new pkg by "-o" option.
Example:
When ftp/wget-devel is moved to ftp/wget, previously you had to run,
% portupgrade -o ftp/wget wget
Now, just run
% portupgrade wget
and portupgrade will do what you want to do.
(4) Try to guess the pkg to be upgraded, when no pkgname is supplied
as a command line argument.
This can be done only when the current directory is under $PORTSDIR.
Example:
Running
% cd /usr/ports/ftp/wget
% portupgrade
will upgrade ftp/wget.
(5) The frequency of INDEX generation on official site is now sufficient,
recommend to run "portsdb -F" (fetch INDEX from official site)
instead of "portsdb -U" (make INDEX by yourself) in portsdb(1). [1]
PR: ports/91164
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org> (maintainer)
Pointed out by: Enrique Matias <cronopios at gmail dot com> [1]
