* Simplify the {BUILD,RUN}_DEPENDS code [1]
* Add a new intlhack component for ports that require intltool >= 0.28
* Add a gstreamerplugins component [2]
* Add an lthack component that takes the place of the standard GNOME
patch-configure [2]
* Add pygtk, pygnome, pygtk2, and pygnome2 components [2]
* Point gnomeaudio to audio/gnomeaudio2 [2]
* Categorize the USE_GNOME component list [2]
Submitted by: Rolf Grossmann <rg@progtech.net> [1]
adamw [2]
"s|-lpthread|${PTHREAD_LIBS}|g ; s|DATADIRNAME=lib|DATADIRNAME=share|g"
has been appearing in many (most?) GNOME port Makefiles lately.
<FreeBSDMarcus> That should clean up quite a few Makefiles.
away with the USE_GNOMNG macro (though I will keep this macro around for
a bit just in case). It also adds GNOME 2 component support.
A new macro has also been introduced called GNOME_DESKTOP_VERSION. Users can
set this in /etc/make.conf or define it when building ports. Current allowed
values are 1 or 2. Depending on the value of this macro, certain ports
may be marked BROKEN if they would conflict with the desired GNOME
desktop version.
Also note, the old USE_GTK, USE_GNOME=yes, USE_IMLIB, USE_ESOUND, and
USE_GLIB are now obsolete. Backwards compatability has been provided,
but those macros should no longer be used.
Special thanks to all the users on freebsd-gnome@ that help test these
patches, and provided feedback. Documentation updates to the FreeBSD
GNOME project site will be forthcoming.
to make GNOME1 platform more modular and will eventually replace bsd.gnome.mk
completely. For the time being, it should be explicitly activated by the
USE_GNOMENG knob, so that it is possible to do gradual conversion.
Reviewed by: marcus, gnome@
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.
not being set properly for some ports. The problem is that ":S" modifier
collapses spaces, even if the regex doesn't match. The following piece of
make(1) "code" illustrates the problem:
foo= a b
.if ${foo} != ${foo:S/x//}
all:
@${ECHO} 'BAD!'
.endif
in bsd.port.mk to support it.
In particular, bsd.port.mk includes bsd.gnome.mk twice (once in the
pre.mk section, once in the post.mk section) and prints out a message
notifying the user of the existence of WITH_* options when one exists.
It also adds MAKE=${GMAKE} to CONFIGURE_ENV when USE_GMAKE is defined.
(This is not related to gnome, but I assume it's useful somewhere and
it shouldn't hurt.)
Submitted by: ade, reg
