Date: Sat, 10 Sep 2011 23:04:56 -0700 From: perryh@pluto.rain.com To: matthias.andree@gmx.de Cc: freebsd-ports@freebsd.org Subject: ports deprecations (was: sysutils/cfs) Message-ID: <4e6c4f88.TEcAbT9xVDyX7ztW%perryh@pluto.rain.com> In-Reply-To: <4E6B374C.5040302@gmx.de> References: <4E651DCF.30605@FreeBSD.org> <201109052146.p85Lkous037023@fire.js.berklix.net> <CADLo838dMd5=TjRF5ffiaPH7o0%2BpeWgaqbQqEfDb3EP-n4ec8A@mail.gmail.com> <4E67935C.6080702@aldan.algebra.com> <CADLo838QkAjq2jPXy_c5MTYW09tZJMvWTNndo3Pnfa3=1c-5Og@mail.gmail.com> <4E68AC85.4060705@icritical.com> <4E68F34C.6090504@FreeBSD.org> <20110909040954.17733a4e@cox.net> <4E6A476D.7090800@gmx.de> <4e6b6f41.hI3BQG0rpsUjddcD%perryh@pluto.rain.com> <4E6B374C.5040302@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthias Andree <matthias.andree@gmx.de> wrote: > Am 10.09.2011 16:08, schrieb perryh@pluto.rain.com: > > Last I knew, if port X uses services provided by port Y and port > > Y changes, port X often needs to be rebuilt and reinstalled even > > though nothing in port X has changed. AFAIK this has nothing to > > do with backups. > > > > If you've found a way to avoid ever having to rebuild, say, > > kdiff3 when something changes in KDE, I'm sure the authors of > > portupgrade and portmaster would like to hear about it! It > > would greatly simplify their job. > > Interesting question that you pose. In cases where only the > so-called SONAME of libraries in port Y changed, but not that > part of the ABI that port X used, chances are we might go without > it for the majority of ports, but that's not done currently. What about the case where Y's API and SONAME did *not* change, but its PORTVERSION or PORTREVISION was bumped to reflect a bugfix? No change to X is needed at all, but * X may still need to be rebuilt (e.g. if Y is statically linked into X's executable(s)), and * portupgrade/portmaster will probably determine that X needs to be rebuilt -- even if it actually doesn't -- because they have no way of determining how pertinent the change in Y was to the way Y is used in X. I believe Conrad's original point[1], that a port (X) may need to be rebuilt and reinstalled even though nothing about it has changed _or needs to change_, stands. [1] http://lists.freebsd.org/pipermail/freebsd-ports/2011-September/070022.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e6c4f88.TEcAbT9xVDyX7ztW%perryh>