From owner-freebsd-ports@FreeBSD.ORG Wed Mar 3 02:05:51 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 DC25216A4CE for ; Wed, 3 Mar 2004 02:05:51 -0800 (PST) Received: from buexe.b-5.de (buexe.b-5.de [80.148.32.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id BABB043D1F for ; Wed, 3 Mar 2004 02:05:50 -0800 (PST) (envelope-from lupe@lupe-christoph.de) Received: from antalya.lupe-christoph.de ([172.17.0.9])i23A5nk25084 for ; Wed, 3 Mar 2004 11:05:49 +0100 Received: from localhost (localhost [127.0.0.1]) by antalya.lupe-christoph.de (Postfix) with ESMTP id 72C8DB88C for ; Wed, 3 Mar 2004 11:05:44 +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 17190-03-6 for ; Wed, 3 Mar 2004 11:05:43 +0100 (CET) Received: by antalya.lupe-christoph.de (Postfix, from userid 1000) id CA8EDB888; Wed, 3 Mar 2004 11:05:43 +0100 (CET) Date: Wed, 3 Mar 2004 11:05:43 +0100 To: ports@FreeBSD.org Message-ID: <20040303100543.GW2562@lupe-christoph.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i From: lupe@lupe-christoph.de (Lupe Christoph) X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at lupe-christoph.de Subject: FWD: [mat@FreeBSD.org: Re: ports/62479: New port: sysutils/munin-node Node-specific part of?Munin] 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: Wed, 03 Mar 2004 10:05:52 -0000 Hi! Mathieu suggested I ask on this mailing list: ----- Forwarded message from Mathieu Arnold ----- From: Mathieu Arnold To: Lupe Christoph Cc: freebsd-gnats-submit@FreeBSD.org Date: Wed, 03 Mar 2004 09:08:54 +0100 Subject: Re: ports/62479: New port: sysutils/munin-node Node-specific part of Munin +-Le 03/03/2004 08:41 +0100, Lupe Christoph a dit : | You added etc/munin/VERSION.node to the plist, which AFAIK causes it to | be removed by portupgrade (pkg_delete, probably). But this is a marker | that is used on upgrades to locate added plugins and automagically link | them to the etc/munin/plugins directory. | I found no way to differentiate between an upgrade and a complete | removal. | What I need on an upgrade is the old plugin directory, and the VERSION | that is being upgraded. BTW, that is also the reason I don't empty the | etc/munin/plugins directory on pkg_delete. | So I think VERSION.node must be removed from plist. Well, badly there is no way to find out wether you're deleting the port or wether you're upgrading :/ and when deleting, a port should remove all it's files. Maybe you should have a look at pkgconfig's plist, maybe you should do the same thing. You can come with this question on ports@ to see what's the way to go :) ----- End forwarded message ----- A little more background: Munin puts a lot of symlinks in etc/munin/plugins. Those point to the real plugins in share/munin/plugins. The symlinks should survive on an upgrade because they are part of the configuration. When munin-node is installed, it checks if there have been new plugins introduced and installs them automagically. It does that based on the old and new version numbers. It works that way on Debian. The Debian package is done by the Munin developers, so I consider that the canonical way. ;-) Opinion poll: 1) Is this behaviour desirable? 2) If yes, is this the best implementation? Thank you for feedback, Lupe Christoph -- | lupe@lupe-christoph.de | http://www.lupe-christoph.de/ | | "Violence is the resort of the violent" Lu Tze | | "Thief of Time", Terry Pratchett |