Date: Thu, 07 Apr 2005 02:18:32 -0400 From: Chuck Swiger <cswiger@mac.com> To: sergei@gnezdov.net Cc: freebsd-questions@freebsd.org Subject: Re: What's the definition of the stale port? Message-ID: <4254D0B8.1060303@mac.com> In-Reply-To: <slrnd59gt6.2u4b.use-reply-to@gnezdov.net> References: <slrnd59bdc.2tpb.use-reply-to@gnezdov.net> <20050407041259.GA69275@xor.obsecurity.org> <slrnd59gt6.2u4b.use-reply-to@gnezdov.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Sergei Gnezdov wrote: > On 2005-04-07, Kris Kennaway <kris@obsecurity.org> wrote: [ ... ] >>> How do I end up having stale ports? >> >> As time marches on :-) > > I am guessing, that port becomes stale after running cvsup. When a new version of a port is committed, anyone running the older version has a stale version. Whether you run cvsup or not doesn't affect whether a new version is available, but you are a lot more likely to notice dependency issues after running cvsup. > So, what exactly are we supposed to accomplish in respect to stale > ports, when we run pkgdb -F (deinstall, some kind of fix, simple > ignore)? pkgdb tries to update the dependencies when new versions of a port appear. Running pkgdb by itself is not especially useful, although you can check and rebuild updated ports by hand. Consider portupgrade instead.... -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4254D0B8.1060303>