Date: Wed, 24 Jul 1996 12:05:34 +0200 (MET DST) From: Stefan Esser <se@zpr.uni-koeln.de> To: "Andrew V. Stesin" <stesin@elvisti.kiev.ua> Cc: asami@cs.berkeley.edu (Satoshi Asami), andreas@klemm.gtn.com, jhs@freebsd.org, ports@freebsd.org Subject: Re: print/gs4 Message-ID: <199607241005.MAA15006@x14.mi.uni-koeln.de> In-Reply-To: <199607230723.KAA17857@office.elvisti.kiev.ua> References: <199607230016.RAA23074@silvia.HIP.Berkeley.EDU> <199607230723.KAA17857@office.elvisti.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew V. Stesin writes: > # I agree with Andreas. No reason to make life unnecesarrily > # complicated. > # > # That this software is NOT covered by GPL is clearly stated in > # pkg/DESCR, what is the problem? > > Think what will you get if you'll install gs4 aka /usr/local/bin/gs; > and later you'll decide to get rid of old gs3.53 stuff as a whole, > so you run pkg_delete on it ;) Maybe we should have some checksum (md5 ?) of each file installed from a port or package in the "+CONTENTS" file ? Before removing any file of a package, all the checksums could be verified, and a warning printed for all files that fail the test. This way you know which config file to preserve for the new version :) With a "force" flag to pkg_delete, all files that did match the checksum could be removed, with a "FORCE" flag, ALL files could be removed unconditionally. And how about making the pkg_delete a part of the installation of the next version of the same port (by some means) ? This way I could just install gs-4.01 and need not bother for files that are to be deleted with no replacement. Kleening up the remains of old ports can be a pain, else ... Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607241005.MAA15006>