From owner-freebsd-ports@FreeBSD.ORG  Sat Jun 16 10:24:31 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@freebsd.org
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id BD6D016A41F
	for <freebsd-ports@freebsd.org>; Sat, 16 Jun 2007 10:24:31 +0000 (UTC)
	(envelope-from shurd@sasktel.net)
Received: from misav07.sasknet.sk.ca (misav07.sasknet.sk.ca [142.165.20.171])
	by mx1.freebsd.org (Postfix) with ESMTP id 7C9FA13C489
	for <freebsd-ports@freebsd.org>; Sat, 16 Jun 2007 10:24:31 +0000 (UTC)
	(envelope-from shurd@sasktel.net)
Received: from bgmpomr1.sasknet.sk.ca ([142.165.72.22]) by misav07 with
	InterScan Messaging Security Suite; Sat, 16 Jun 2007 03:54:29 -0600
Received: from server.hurd.local
	(adsl-76-202-204-41.dsl.lsan03.sbcglobal.net [76.202.204.41])
	by bgmpomr1.sasknet.sk.ca (SaskTel eMessaging Service)
	with ESMTPA id <0JJQ00I1K3ISCS00@bgmpomr1.sasknet.sk.ca> for
	freebsd-ports@freebsd.org; Sat, 16 Jun 2007 03:54:29 -0600 (CST)
Date: Sat, 16 Jun 2007 02:54:27 -0700
From: Stephen Hurd <shurd@sasktel.net>
In-reply-to: <20070615121125.GH1173@turion.vk2pj.dyndns.org>
To: Peter Jeremy <peterjeremy@optushome.com.au>
Message-id: <4673B353.5040006@sasktel.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
References: <20070614070602.GD39533@obiwan.tataz.chchile.org>
	<200706140714.l5E7EK0U023767@smtpclu-1.eunet.yu>
	<20070614075418.GA8093@obiwan.tataz.chchile.org>
	<200706142322.l5ENMbZt009741@smtpclu-6.eunet.yu>
	<20070615121125.GH1173@turion.vk2pj.dyndns.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.2)
	Gecko/20070523 SeaMonkey/1.1.1
Cc: Nikola Lecic <nlecic@EUnet.yu>, Jeremie Le Hen <jeremie@le-hen.org>,
	freebsd-ports@freebsd.org
Subject: Re: Keeping track of automatically installed dependency-only ports
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jun 2007 10:24:31 -0000

Peter Jeremy wrote:
> For an opposing PoV: I often see ports that looks interesting or look
> like a possible solution to a problem and will install the port to
> have a play.  If it turns out that it's not suitable, I would like to
> be able to easily unistall the port and any dependencies it pulled in
> that I didn't already have.  Currently, this is a fairly delicate
> operation and I usually base it on timestamps within /var/db/pkg.
>   

All of this rather assumes that *everything* is installed from ports. 

1) install portXXX which requires SDL, so SDL gets sucked in
2) build thingYYY (which uses configure and only uses SDL if it's 
already installed - common) manually and install it
3) remove portXXX (which takes SDL away since I didn't add it to 
KEEPFOREVER not knowing it was a dependency)
4) Six days later my wife calls me at work complaining that thingYYY 
doesn't work anymore and what did I do to break it?

Surely we are not assuming that everything anyone wants is in the ports 
system are we?