On Nov 9, 2008, at 22:05, William Davis wrote:
On Nov 9, 2008, at 10:33 PM, Ryan Schmidt wrote:
On Nov 9, 2008, at 21:12, William Davis wrote:
On Nov 9, 2008, at 9:49 PM, Ryan Schmidt wrote:
On Nov 9, 2008, at 08:03, William Davis wrote:
RSS just told me:
Commit by [EMAIL PROTECTED] :: r41701 /trunk/base/src/
port/portindex.tcl: (link)
http://trac.macports.org/changeset/41701
portindex.tcl: Generate the port index in a temporary file
first, then replace the PortIndex file all at once; fixes #16234
If this is the case cant we easily update the index more than
twice a day now? Perhaps even every half hour?
I don't think my commit changes anything for the frequency of
portindex updates. All it does is make sure that until the new
portindex is done being regenerated, the old portindex is still
around so it can be used by other port operations.
I don't know why the portindex is only regenerated every 12 hours.
Ryan, I know you didnt change the update frequency. My point was
that with your change in place it seems possible AFTERWARDS to
update the index more frequently now that the old index can be
used while the new one is building.
I didn't think the server used the portindex for anything.
It doesnt as far I know, but the people who are running selfupdate
do, dont they?
Surely the portindex is generated in one place (like where the svn
working copy of dports is) and then this is synced to another place
(the one where rsync syncs from). So even now there should never be a
time when a user syncs and gets an incomplete portindex.
The only reason for the above ticket/commit is that I occasionally
want to regenerate the portindex on my local machine, but during the
minutes that takes to run, I might want to also do other things with
MacPorts. Now I can.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
