Date: Fri, 17 May 2002 15:47:45 -0700 From: "Philip J. Koenig" <pjklist@ekahuna.com> To: questions@FreeBSD.ORG Cc: Brian Minard <bminard@flatfoot.ca> Subject: Re: Portupgrade / pkgdb question Message-ID: <20020517224745963.AAA345@empty1.ekahuna.com@pc02.ekahuna.com> In-Reply-To: <15589.21588.23312.302422@yop.flatfoot.ca> References: <20020517132846380.AAA341@empty1.ekahuna.com@pc02.ekahuna.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 May 2002, at 15:04, Brian Minard boldly uttered: > On May 17, 2002, Philip J. Koenig wrote: > > It appears that ports or packages created back in the 4.1 days aren't > > aware of "origin", so you have to 'correct' all of them. (very > > tedious without some form of prompting when running pkgdb -F, IMHO.. > > especially when you have 200+ packages/ports installed) > > > > Just a thought: Why not update the ports tree? > > When I moved from the 4.0 CD to the 4.6 pre-release, I cvsup'ed the > ports tree and then executed the following. > > # portsupgrade -cO > upgrade.sh > (edit upgrade.sh to remove the packages you really don't want upgraded) > # sh upgrade.sh > # portsdb -Uu > # pkgdb -F (with a much smaller number of out of date origins...) > > In this case, all installed ports are upgraded to their current > versions. This seems to have worked well. I avoided the interactive > ports and didn't meet with much success building KDE. I assume "portsupgrade" was a typo. The reason I haven't bothered with that is that according to the portupgrade manpage, you're in for trouble if you try to upgrade a bunch of ports and you don't have an error-free pkgdb. Since pkgdb -F implies my installed packages (most installed originally as binary packages from the 4.1 CD) don't even know where to check to see if they're up to date and/or what port to build to upgrade themselves (they don't understand "origin" and portversion lists most packages with the "#" character so can't even report if they're up to date or not) I don't see how that would work. Also, why would simply redirecting standard output to a file avoid portupgrade running anyway? I would think that would just send the runtime messages to a file? Aren't you thinking of pkg_version -c? Pkg_version appears to be able to determine versions without a valid "origin", unlike portversion/portupgrade. I already CVSup'd the ports tree (same time I got the sources for (4.6-PRE), ran "portsdb -Uu", and "pkgdb -F", the latter being the sticking point. > (Might want to look at pkgtools.conf before you try this.) > > If you use portsclean (-CDD) things should get cleaned up afterwards. -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020517224745963.AAA345>