From owner-freebsd-questions Tue Apr 24 5:41: 9 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id AA41637B424 for ; Tue, 24 Apr 2001 05:41:06 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 25494 invoked by uid 100); 24 Apr 2001 12:40:55 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15077.29783.160802.254310@guru.mired.org> Date: Tue, 24 Apr 2001 07:40:55 -0500 To: Jonathan Chen Cc: questions@freebsd.org, dan@langille.org Subject: Re: upgrading a port which depends on other ports In-Reply-To: <41429711@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Chen types: > On Tue, Apr 24, 2001 at 12:35:52PM +1200, Dan Langille wrote: > > What's the recommend procedure when upgrading a port? Here's an example: > > > > # pkg_delete gtk-1.2.8 > > pkg_delete: package `gtk-1.2.8' is required by these other packages > > and may not be deinstalled: > > imlib-1.9.8.1 > > fnlib-0.5 > > [other 33 ports snipped] > > > > Now how would you go about installing the latest gtk? > > You _could_ force a package-delete with the '-f' option, but I dunno > what that would break in terms of applications that depend on it. That's actually the recommended way to upgrade ports in this case. > If > you're lucky nothing; if the library has changed radically, all > dependant applications will stop working. > The safest way (which also happens to be the most time-consuming one) > is to delete the dependancies as well, and rebuild them once the new > library is in. If the library has changed radically enough, all dependent applications will stop working in this case as well. In the worst case, they'll fail to build because something like the include file structure has changed, and the dependency test they used fails to reinstall the old version. Of course, reinstalling the old version on top of the new one may well be worse than failing to build. Which is all part of why pkg_version -c has an exit in it. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message