ports/59682: portupgrade uses ports when you want it to use packages
smckay at internode.on.net
Tue Nov 25 14:00:47 UTC 2003
>Synopsis: portupgrade uses ports when you want it to use packages
>Arrival-Date: Tue Nov 25 06:00:39 PST 2003
>Originator: Stephen McKay
>Release: FreeBSD 4.9-RELEASE i386
I'm updating a machine to 4.9-RELEASE, and upgrading all the
ports too. I've mirrored all the packages locally, and I'm
trying to get portupgrade to stop downloading and building
ports from source. The -PP flag should do that but it is not
always effective, as shown here:
** Package name changed from 'gtk-thinice-engine' (x11-toolkits/gnome-themes) to
---> Upgrading 'gtk-thinice-engine-2.0.2' to 'gnome-themes-2.4.0' (x11-toolkits
---> Building '/usr/ports/x11-toolkits/gnome-themes'
Even though gnome-themes-2.4.0.tgz (the package) was there for the
taking, portupgrade downloaded the source and started compiling it.
Heck, by that point in the upgrade, gnome-themes was probably at
2.4.0 already, so that's doubly bad.
Since the ports build system was now in charge, all sorts of stuff
was pulled in and built from source, even though prebuilt packages
for all of them were ready to be installed. Eventually it all fell
over since port building code doesn't do upgrading very well.
"portupgrade -PP gtk-thinice-engine" seems to do it for me.
More information about the freebsd-ports-bugs