Fwd: [40828] contrib/mpab/chroot-scripts/buildports

Bryan Blackburn blb at macports.org
Fri Oct 17 00:30:03 PDT 2008


On Fri, Oct 17, 2008 at 08:54:42AM +0200, C. Florian Ebeling said:
> Hi Bryan,
> 
[...]
> -      portOutput=`/opt/local/bin/port -dvf uninstall $uninstallPort 2>&1`
> +      portOutput=`/opt/local/bin/port -dvf deactivate $uninstallPort 2>&1`
>        if [[ $? != 0 ]]; then
>           echo $portOutput
>           break
> 
> I think this breaks things a bit. Running my little build server script
> I noticed many more failing builds. They complain ultimately about
> the port in question already being installed, after otherwise building fine.
> 

Is it running a trunk build?  It definitely had no issues with my trunk
build, but I didn't try it against a 1.6 build.

> This is due to the somewhat surprising behaviour that when
> a port is deactivated and you run "port install", it builds right away
> not looking if there was a deactivated one of the same version. Then
> it tries to activate as well, and that fails. One could argue that install
> should resolve a by looking at deactivated installs first, though.
> 
> Florian
> 
> 
> -- 
> Florian Ebeling
> Twitter: febeling
> florian.ebeling at gmail.com


More information about the macports-dev mailing list