From owner-freebsd-ports@FreeBSD.ORG Sun Jun 6 23:53:34 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 565A31065674 for ; Sun, 6 Jun 2010 23:53:34 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [213.150.42.155]) by mx1.freebsd.org (Postfix) with ESMTP id C01728FC16 for ; Sun, 6 Jun 2010 23:53:33 +0000 (UTC) Received: from [10.10.1.200] (1385165082.dhcp.dbnet.dk [82.143.241.26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id DED9663A6B0 for ; Mon, 7 Jun 2010 01:53:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1275868412; bh=Xu8YiWpbD27yGqsadGGmI7E+p9YW/Mq5m57v4DjRslo=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=tR73qWKmxz/6jPpF3ttACjRY+rKqa1dJllnUFddallQ2GsTznc5oRt3hDdm81DJVP EVR3mlIyvjTxD5cUnQ/2PuL2Jd2PxprP4ArVTadtAq5kwBjz/KAQo5oDFfc5lP4Vh2 dFadnpC8GqGNzvR64amkQ09wLiy+zmuE5rg/vCDw= Message-ID: <4C0C34FC.4030603@gibfest.dk> Date: Mon, 07 Jun 2010 01:53:32 +0200 From: Thomas Rasmussen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Manually registering dependencies for ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2010 23:53:34 -0000 Hello, I've been wondering about something: When I write a script or webapp that needs some port to run, like a perl module, I install the needed port and life is good (tm). A year later when I've completely forgotten about the script I go do some spring-cleaning of the ports on the server, and I see some perl module that doesn't have any dependencies, and delete it. Fast forward a few days when I discover the script doesn't work anymore, cue face-palm, remove bullet from foot, etc. Is there some way I can register a dependency to prevent this ? Like adding a flag to an installed port to say "something outside of the ports system depends on this" along with a user specified comment string. A system like that could result in something like this: pkg_delete -x p5-something pkg_delete: p5-something cant be uninstalled because: "somescript.pl uses this module, for the love of everything good do not delete it" Is something like this already implemented, or does anyone have suggestions to where I might begin if I want to make this ? Am I the only FreeBSD admin absent-minded enough to have this problem ? :) Best regards Thomas Steen Rasmussen PS: I know that this kind of hand-holding is uncommon in FreeBSD. We allow all kinds of foot-shooting, but a safeguard like this would be a nice improvement to an (IMO) already excellent ports system.