From owner-freebsd-ports@FreeBSD.ORG Fri Dec 10 07:22:39 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4AC416A4CE for ; Fri, 10 Dec 2004 07:22:39 +0000 (GMT) Received: from buexe.b-5.de (buexe.b-5.de [80.148.32.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0045D43D4C for ; Fri, 10 Dec 2004 07:22:37 +0000 (GMT) (envelope-from lupe@lupe-christoph.de) Received: from antalya.lupe-christoph.de (antalya.lupe-christoph.de [172.17.0.9])iBA7MV8g001098; Fri, 10 Dec 2004 08:22:31 +0100 Received: from localhost (localhost [127.0.0.1]) by antalya.lupe-christoph.de (Postfix) with ESMTP id 54AE3B886; Fri, 10 Dec 2004 08:22:26 +0100 (CET) Received: from antalya.lupe-christoph.de ([127.0.0.1]) by localhost (antalya [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 28711-03-2; Fri, 10 Dec 2004 08:22:24 +0100 (CET) Received: by antalya.lupe-christoph.de (Postfix, from userid 1000) id C1C61B885; Fri, 10 Dec 2004 08:22:24 +0100 (CET) Date: Fri, 10 Dec 2004 08:22:24 +0100 From: Lupe Christoph To: Kris Kennaway Message-ID: <20041210072224.GD3113@lupe-christoph.de> References: <20041208094448.GA18514@lupe-christoph.de> <20041208214203.GA10122@xor.obsecurity.org> <20041209052634.GX3113@lupe-christoph.de> <20041209225434.GA5933@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209225434.GA5933@xor.obsecurity.org> User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at lupe-christoph.de cc: freebsd-ports@freebsd.org Subject: Re: Mediation needed for munin-node and munin-main X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 07:22:39 -0000 On Thursday, 2004-12-09 at 14:54:34 -0800, Kris Kennaway wrote: > On Thu, Dec 09, 2004 at 06:26:34AM +0100, Lupe Christoph wrote: > > The default set is determined by running munin-node-configure which > > loads each plugin in turn and asks it if it can autoconfigure and if it > > is a generic plugin (e.g. if_) about suggested suffixes. This is quite > > time-consuming. ... > How time-consuming? Pentium MMX 100 MHz: 26 sec Athlon 1000 MHz: 5 sec VMware on Athlon XP 2000: 12 sec Not as much as I thought. It's still a lot of work to determine and compare the plugin set from this output: Plugin | Used | Suggestions ------ | ---- | ----------- cpu | no | yes df | no | yes ... I'd collect all plugins that have a "yes" in the "Suggestions" column in a string and compare that against a string containing the existing symlink names. Lines like this if_ | no | yes +em0 +em1 +fxp0 +fxp1 +fxp2 +fxp3 +fxp4 +fxp5 make this especially hard. But it's doable. Just ugly. > > > It's an important requirement that doing 'make install deinstall' > > > (alternatively pkg_add; pkg_delete) leaves the system in the same > > > state it was before the 'install', and not leave behind random cruft > > > in ${PREFIX}. > > Well, I need at least VERSION. And the user would not like munin-main to > > delete all the data files that have been accumulated while the port was > > installed. > > I cannot ask the user if he wants all files deleted with a default of > > "yes" because many people will just blindly hit return. And if the > > default is "no", the automated removal will leave "cruft" behind. > I meant 'installed and immediately deinstalled', i.e. leave nothing > behind if nothing is changed from the default installation. If the > administrator changes something, it should be preserved after > deinstallation. This is how ports are supposed to work. Can't. VERSION.node is left unchanged but needed. Either I satisfy your requirements, or I deviate from the behaviour of all other Munin packages when deinstalling. IIRC, Debian has a "configfiles" category. A Debian package can be just removed which leaves them behind, or it can be removed with the --purge option which eradicates them. This distiction is exactly what is missing in the FreeBSD ports. I never looked at the Debian package upgrade process in detail, but I'd guess an upgrade is just a remove followed by an install, just like a FreeBSD port. Except that configfiles are left untouched because the --purge option is not used. Thank you, Lupe Christoph -- | lupe@lupe-christoph.de | http://www.lupe-christoph.de/ | | "... putting a mail server on the Internet without filtering is like | | covering yourself with barbecue sauce and breaking into the Charity | | Home for Badgers with Rabies. Michael Lucas |