MacPorts 2.1.0 has been released - problems with the progress lines

[Bjarne D Mathiesen]

I've noticed these two new lines in my output:
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%

My problem is with the progress of the percentages in combination with
updating ports automatically using a script in periodic daily logging to
syslog. That leads to this :

--->  Updating database of binaries
--->  Updating database of binaries: 0.0%
--->  Updating database of binaries: 0.0%
--->  Updating database of binaries: 0.0%
--->  Updating database of binaries: 0.0%
--->  Updating database of binaries: 0.0%
--->  Updating database of binaries: 0.0%
--->  Updating database of binaries: 0.0%
--->  Updating database of binaries: 0.0%
--->  Updating database of binaries: 0.1%
--->  Updating database of binaries: 0.1%
--->  Updating database of binaries: 0.1%
--->  Updating database of binaries: 0.1%
--->  Updating database of binaries: 0.1%
--->  Updating database of binaries: 0.1%
--->  Updating database of binaries: 0.1%
--->  Updating database of binaries: 0.1%
--->  Updating database of binaries: 0.2%
--->  Updating database of binaries: 0.2%
--->  Updating database of binaries: 0.2%
--->  Updating database of binaries: 0.2%
--->  Updating database of binaries: 0.2%
--->  Updating database of binaries: 0.2%
--->  Updating database of binaries: 0.2%
--->  Updating database of binaries: 0.3%
--->  Updating database of binaries: 0.3%
--->  Updating database of binaries: 0.3%
--->  Updating database of binaries: 0.3%

... seveal hundred lines later ...

--->  Updating database of binaries: 99.7%
--->  Updating database of binaries: 99.7%
--->  Updating database of binaries: 99.7%
--->  Updating database of binaries: 99.7%
--->  Updating database of binaries: 99.7%
--->  Updating database of binaries: 99.7%
--->  Updating database of binaries: 99.7%
--->  Updating database of binaries: 99.7%
--->  Updating database of binaries: 99.8%
--->  Updating database of binaries: 99.8%
--->  Updating database of binaries: 99.8%
--->  Updating database of binaries: 99.8%
--->  Updating database of binaries: 99.8%
--->  Updating database of binaries: 99.8%
--->  Updating database of binaries: 99.8%
--->  Updating database of binaries: 99.8%
--->  Updating database of binaries: 99.9%
--->  Updating database of binaries: 99.9%
--->  Updating database of binaries: 99.9%
--->  Updating database of binaries: 99.9%
--->  Updating database of binaries: 99.9%
--->  Updating database of binaries: 99.9%
--->  Updating database of binaries: 99.9%
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors
--->  Scanning binaries for linking errors: 0.0%
--->  Scanning binaries for linking errors: 0.0%
--->  Scanning binaries for linking errors: 0.1%
--->  Scanning binaries for linking errors: 0.1%
--->  Scanning binaries for linking errors: 0.2%
--->  Scanning binaries for linking errors: 0.2%
--->  Scanning binaries for linking errors: 0.2%
--->  Scanning binaries for linking errors: 0.3%
--->  Scanning binaries for linking errors: 0.3%
--->  Scanning binaries for linking errors: 0.4%
--->  Scanning binaries for linking errors: 0.4%
--->  Scanning binaries for linking errors: 0.4%
--->  Scanning binaries for linking errors: 0.5%
--->  Scanning binaries for linking errors: 0.5%
--->  Scanning binaries for linking errors: 0.6%
--->  Scanning binaries for linking errors: 0.6%
--->  Scanning binaries for linking errors: 0.6%
--->  Scanning binaries for linking errors: 0.7%
--->  Scanning binaries for linking errors: 0.7%
--->  Scanning binaries for linking errors: 0.8%
--->  Scanning binaries for linking errors: 0.8%
--->  Scanning binaries for linking errors: 0.8%
--->  Scanning binaries for linking errors: 0.9%
--->  Scanning binaries for linking errors: 0.9%
--->  Scanning binaries for linking errors: 1.0%

... several hundred lines later ...

--->  Scanning binaries for linking errors: 99.1%
--->  Scanning binaries for linking errors: 99.1%
--->  Scanning binaries for linking errors: 99.1%
--->  Scanning binaries for linking errors: 99.2%
--->  Scanning binaries for linking errors: 99.2%
--->  Scanning binaries for linking errors: 99.3%
--->  Scanning binaries for linking errors: 99.3%
--->  Scanning binaries for linking errors: 99.3%
--->  Scanning binaries for linking errors: 99.4%
--->  Scanning binaries for linking errors: 99.4%
--->  Scanning binaries for linking errors: 99.5%
--->  Scanning binaries for linking errors: 99.5%
--->  Scanning binaries for linking errors: 99.5%
--->  Scanning binaries for linking errors: 99.6%
--->  Scanning binaries for linking errors: 99.6%
--->  Scanning binaries for linking errors: 99.7%
--->  Scanning binaries for linking errors: 99.7%
--->  Scanning binaries for linking errors: 99.7%
--->  Scanning binaries for linking errors: 99.8%
--->  Scanning binaries for linking errors: 99.8%
--->  Scanning binaries for linking errors: 99.9%
--->  Scanning binaries for linking errors: 99.9%
--->  Scanning binaries for linking errors: 100.0%
--->  Found 19 broken file(s), matching files to ports
--->  Found 3 broken port(s), determining rebuild order
--->  Rebuilding in order
     php5 @5.3.13 +apache2+pear+suhosin
     kismet @2011-01-R1
     snort @2.9.1.2
--->  Computing dependencies for php5

And this is for every port that's getting updated :-(

This new feature has completely messed up my daily.out log :-(

Is there something I can do to switch this progess thingy off ???


-- 
Bjarne D Mathiesen
København N ; Danmark ; Europa
----------------------------------------------------------------------
denne besked er skrevet i et totalt M$-frit miljø
MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3