Date: Tue, 22 Aug 2006 15:27:11 -0700 From: "Kevin Oberman" <oberman@es.net> To: "Todorov @ Paladin" <todorov@paladin.bulgarpress.com> Cc: Vivek Khera <vivek@khera.org>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: 5.5 to 6.1 upgrade Message-ID: <20060822222711.C52BE45055@ptavv.es.net> In-Reply-To: Your message of "Tue, 22 Aug 2006 23:07:45 %2B0300." <44EB6411.4040406@paladin.bulgarpress.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Tue, 22 Aug 2006 23:07:45 +0300 > From: "Todorov @ Paladin" <todorov@paladin.bulgarpress.com> > Sender: owner-freebsd-stable@freebsd.org > > Vivek Khera написа: > > > > On Aug 22, 2006, at 2:56 PM, Todorov @ Paladin wrote: > > > >>> don't find this out the hard way :-( > >>> > >> How to find which is dynamically using libs and which application is > >> not? > >> > >> This is something I was wondering before... > >> > >> Thank you in advance. > > > > path of least resistance: upgrade everything. :-) > > > > sometimes it is easier to start from scratch with a CD or network > > install. > > > Something related to this topic - where are the options we choose for a > specific port saved? Also - why portupgrade is not always aware of > previously chosen options for a port build? This is rather new and not as well publicized as it might have been. As ports are updated, configuration options are stored in /var/ports/PORTNAME/options. If you want to flush this for a port, 'make rmconfig' will do the job. You will be asked for options the next time you make the port, or you can 'make config' on a port to have it ask again. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060822222711.C52BE45055>