On Nov 10, 2008, at 12:19 AM, Joshua Root wrote:
William Davis wrote:
I'll try one more time: Ryan made a change that will cause
portindex to
be updated all at once by building it in a temp file and then
overwritting the old file all at once.
THEREFORE
there will be no problem with sections of portindex being locked when
someone runs selfupdate.
THEREFORE
unless there are other constrains, it should now be possible to
update
portindex more often without end-users having problems.
Server-side, the new PortIndex is only committed to svn after it is
finished being regenerated, so an end user could never get a partial
index from rsync.
The issue with there being a partial index was only present when the
index in a local ports tree was rebuilt. The one advantage to end
users
of updating the PortIndex more often would be that new ports would be
available sooner.
- Josh
No doubt you are quite right. Still I wonder where those error mesgs
saying something about port foo being updated I sometimes get inserted
into the middle of the file list as its copyed down come from......
But! getting updates more often was indeed the point......
William Davis
frstanATbellsouthDOTnet
Mac OS X.5.5 Darwin 9.5.0
XQuartz 2.3.2 (xorg-server 1.4.2-apple21)
Mac Mini Intel Duo @ 1.86 GHz
Mundus vult decepi, ego non
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
