Date: Sat, 15 Oct 2005 15:08:38 -0400 (EDT) From: Peter Matulis <petermatulis@yahoo.ca> To: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: portupgrade -ar (why?) Message-ID: <20051015190838.86886.qmail@web60012.mail.yahoo.com> In-Reply-To: <Pine.GSO.4.62.0510151929020.17106@mail.ilrt.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Jan Grant <Jan.Grant@bristol.ac.uk> wrote: > On Sat, 15 Oct 2005, Peter Matulis wrote: > > > What is the use of specifying the 'r' switch when using the 'a' > > switch? > > > > # portupgrade -ar > > > > This says to upgrade all ports plus the ones that depend on all > > those ports. Am I missing something? Wouldn't "the ones that > > depend" be upgraded anyway? > > Not necessarily. For instance: package P might use library L. A > change in L might alter the size and layout of structures exposed to P. > The source-level API of L is unchanged; the binary-level ABI is > altered. So whilst the source code of P might not have changed, it might (for > instance) be using a macro defined by a header in L that will look > at the wrong offset in the new structure. These kinds of ABI > compatibility problems can be fixed by recompilihng P. But still, a port requires upgrading or it does not. Using 'r', portupgrade ultimately checks whether some port should be upgraded. Are you saying that the 'r' switch involves a different decision making process than 'a'? __________________________________________________________ Find your next car at http://autos.yahoo.ca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051015190838.86886.qmail>