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

[C. Florian Ebeling]

Hi Bryan,

---------- Forwarded message ----------
From:  <blb at macports.org>
Date: Wed, Oct 15, 2008 at 9:58 PM
Subject: [40828] contrib/mpab/chroot-scripts/buildports
To: macports-changes at lists.macosforge.org


Revision 40828 Author blb at macports.org Date 2008-10-15 12:58:26 -0700
(Wed, 15 Oct 2008)

Log Message

Use deactivate instead of uninstall to speed up cleanup times between
each port build

Modified Paths

contrib/mpab/chroot-scripts/buildports

Diff

Modified: contrib/mpab/chroot-scripts/buildports (40827 => 40828)

--- contrib/mpab/chroot-scripts/buildports	2008-10-15 19:53:00 UTC (rev 40827)
+++ contrib/mpab/chroot-scripts/buildports	2008-10-15 19:58:26 UTC (rev 40828)
@@ -34,7 +34,7 @@
 {
    installedPorts=`/opt/local/bin/port installed | /usr/bin/tail +2 |
/usr/bin/awk '{print $1}'`
    for uninstallPort in $installedPorts; do
-      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.

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