Date: Thu, 13 Jan 2000 07:56:32 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/pkg_install/delete perform.c Message-ID: <00Jan13.075634est.40339@border.alcanet.com.au> In-Reply-To: <200001121837.KAA29133@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Thu, Jan 13, 2000 at 05:30:53AM %2B1100 References: <20000112131941.A27482@rtfm.net> <200001121837.KAA29133@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2000-Jan-13 05:30:53 +1100, "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> wrote: >Actually a better modification is to stop using the version of the >name of the directory all togeather and store it inside the directory, >one thing this would fix is installing over the top of an existing >port with a newer port and then pkg_delete of the older port leaving >you screwed up. Or not pkg_delete the old port and leaving cruft/wrong >files around. I presume you mean that pkg_install does something like: 1) Install files in the new port that don't already exist 2) Replace files that are updated by the new port 3) Leave files that no longer exist. This is still likely to leave un-needed cruft lying around (ie files that were part of the old port, no longer exist in the new port and are no longer necessary). Unfortunately, I don't believe it's possible to automate the `remove no longer needed cruft' step, since the `no longer needed cruft' can depend on: - the installed version of the port - what other ports depend on that port - the new version of the port - what non-port tools the user might have installed that depend on the port. In some cased, the unwanted cruft needs to be deleted. As an example, teTeX-0.4, but not the current version, helpfully installs its own copy of makeinfo into /usr/local/bin. This version of makeinfo is much older than the one in /usr/bin and breaks world. Tcl (and Tk) are also particularly good (or should that be bad) examples of tools where newer versions are often not backwardly compatible with older versions. I'm not sure what the correst behaviour should be. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00Jan13.075634est.40339>