- "files/patch-ae" is no longer required
- PLIST substitution is used to merge the files "pkg-plist.doc" and
"pkg-plist" into one entity
- new patch file "files/patch-static.scm" has been added
Approved by: alex [MAINTAINER]
package name became fpx-1.2.0-3 -- the extra dash problem... It was
quickly pointed out to me by KATO Tsuguru and Lev Serebryakov, with
the former providing the simple patch I commit now. The package is
now fpx-1.2.0.3.
Fortunately, dot follows dash in the sorting order, so there is no
need to mess with the PORTREVISION.
Submitted by: KATO Tsuguru
1. Redesigned -demo GUI (nice, except see below).
2. New modes of operation; one saver, blank/don't blank.
3. New hacks (screen saver modules).
4. Improved or fixed several other hacks.
5. Improved xinerama compatibility.
See http://www.jwz.org/xscreensaver/changelog.html for details.
* Sadly, the new GUI relies on xml, so that's now a dependency.
* I moved the various hack files and their xml config files into
their own directories.
* Fixed the poorly done hack in the Makefile to s/malloc.h/stdlib.h/
* Removed a patch hunk that's no longer needed.
* Added a fix for the new configure script's failure to recognize the
option to put the xml files in their own directories. (Already contacted author)
# This is done over my last commit from 4.0.1 to 4.2.
- Change maintainer to Jos Backus <josb@cncdsl.com>.
# Chuckr seems too busy to respond queries.
PR: ports/33553
Submitted by: New maintainer
down to user support flaws in the FreeBSD ports system. The flaw in question
is related to the fact that dependencies are often "chained", which allows to
simplify maintenance of ports with large number of implied dependencies (a la
Evolution, Nautilus, you-name-it). Dependency chaining it's not a problem by
itself, but the fact that when building or installing a port the system doesn't
check chain integrity - it's only checks that dependencies explicitly
specified in port's Makefile are satisfied, which opens wide window for
various hard-trackable problems when one or more links in the middle of the
chain missed.
The idea behind the tool is quite simple - it should be executed right after
main dependency checking procedure, two times for each build - check build-time
chain before building the port (pre-pre-extract) and check run-time chain
before installing the port (pre-pre-install). When executed, the tool checks
integrity of the specified chain (build-time, run-time or both) and reports all
errors, both fatal (dependency isn't installed) and non-fatal (dependency is
installed, but different version).
I've wrote this tool mostly to simplify maintenance of the GNOME ports, but
it doesn't contain anything GNOME-specific, so that it could be used in the
other parts of tree as well.
As an example I've added GNOME_VALIDATE_DEPS_CHAIN knob into bsd.gnome.mk (off
by default), which enables automatic chain validation for all ports that
USE_GNOMELIBS. This is a bit hackish, because I've used pre-extract and
pre-install targets - what we probably need is a generic way to plug various
custom tasks specified in bsd.xxx.mk (where xxx is kde, gnome, python, etc.)
into various parts of the build process (something like {pre,post}-pre-foo,
{pre,post}-post-foo springs into my mind).
The code is quite raw, so that I would appreciate any bug reports, patches,
suggestions, constructive critiquie and so on.
branch, and fixes a security hole (which was patched in the last commit
to the port).
PR: 33610
Submitted by: Udo Schweigert <udo.schweigert@siemens.com>
Approved by: silence from maintainer
