portindex updates

[William Davis]

On Nov 9, 2008, at 11:24 PM, Bryan Blackburn wrote:

> On Sun, Nov 09, 2008 at 11:05:22PM -0500, William Davis said:
>>
>> 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 ryandesign at macports.org :: 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?
>
> That change to portindex only affects when you run it, using  
> selfupdate
> simply gets the new PortIndex from the server.  Hence, this  
> shouldn't be
> affecting you unless you also have a local repository and run  
> portindex on
> it (which I think was the initial reason for the ticket which  
> resulted in
> the change).
>
> Bryan


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.

Im speaking here from the end-user's point of view.



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