From owner-cvs-all Sun Jan 13 4: 5:16 2002 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 32F5337B41F; Sun, 13 Jan 2002 04:05:10 -0800 (PST) Received: (from sobomax@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0DC59712494; Sun, 13 Jan 2002 04:05:09 -0800 (PST) (envelope-from sobomax) Message-Id: <200201131205.g0DC59712494@freefall.freebsd.org> From: Maxim Sobolev Date: Sun, 13 Jan 2002 04:05:09 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: ports/Tools/scripts chkdepschain.py ports/Mk bsd.gnome.mk X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sobomax 2002/01/13 04:05:09 PST Modified files: Mk bsd.gnome.mk Added files: Tools/scripts chkdepschain.py Log: Add chkdepschain.py - a tool to address one of the most annoying when it comes 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. Revision Changes Path 1.13 +22 -1 ports/Mk/bsd.gnome.mk 1.1 +294 -0 ports/Tools/scripts/chkdepschain.py (new) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message