Date: Sat, 16 Jun 2007 02:54:27 -0700 From: Stephen Hurd <shurd@sasktel.net> To: Peter Jeremy <peterjeremy@optushome.com.au> 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 Message-ID: <4673B353.5040006@sasktel.net> In-Reply-To: <20070615121125.GH1173@turion.vk2pj.dyndns.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4673B353.5040006>