[prev in list] [next in list] [prev in thread] [next in thread] 

List:       macports-dev
Subject:    Re: Adding distfiles to the repository
From:       Ryan Schmidt <ryandesign () macports ! org>
Date:       2008-07-22 3:33:37
Message-ID: 1A7AD9FC-612B-46EA-8998-64A26C6DD1A3 () macports ! org
[Download RAW message or body]

On Jul 21, 2008, at 14:56, William Siegrist wrote:

> On Jul 18, 2008, at 10:45 AM, William Siegrist wrote:
>
>> On Jul 17, 2008, at 4:08 PM, Blair Zajac wrote:
>>
>>> William Siegrist wrote:
>>>
>>>> On Jul 17, 2008, at 3:09 PM, Ryan Schmidt wrote:
>>>>
>>>>> On Jul 17, 2008, at 17:01, Blair Zajac wrote:
>>>>>
>>>>>> William Siegrist wrote:
>>>>>>
>>>>>>> please allow at least 24hr after a portfile is updated
>>>>>>> before complaining though, as the mirror is only updated daily.
>>>>>>
>>>>>> Thanks for this info.  Can we up the cron from 24 to something  
>>>>>> on a shorter basis?
>>>>>
>>>>> This may be relevant for the php5-devel port as well. It's  
>>>>> currently tracking php 5.2 release candidates but I now have a  
>>>>> request from a user who wants to try a feature only available  
>>>>> in php 5.3. The php team provides snapshot tarballs of php 5.3,  
>>>>> but they're generated every two hours, and disappear after ten  
>>>>> hours. So I would have to make sure to time my commit such that  
>>>>> it's less than ten hours until the portmirror process runs on  
>>>>> the distfiles mirror machine. Which I could do. But it would be  
>>>>> convenient if I wouldn't have to remember to do that. Who knows  
>>>>> what time of day I might feel like working on my ports.
>>>>
>>>> The current process takes 6-8 hours to run and eats a decent  
>>>> amount of cpu cycles because it tries to mirror every variant of  
>>>> every port, so doing it more often wont work well on the server.  
>>>> Like I've said before, this allows for daily re-trying if the  
>>>> mirroring fails the first day.  What I could do is add a mirror  
>>>> attempt during post-commit as well. So every port gets mirrored  
>>>> upon commit and then once a day after that. When you commit, if  
>>>> your distfile is unavailable, it'll get retried the next morning  
>>>> during the daily job.  I think this is reasonable and covers  
>>>> everyone's needs.
>>>
>>> That sounds good.
>>
>> I have a slightly-tested job in place for post-commit mirroring.  
>> It will send email to maintainers if mirroring fails, much like  
>> how lint nags you.
>
> The post-commit mirroring seems to be working and no one has  
> complained about emails nagging them with errors.
>
> Ryan, let me know if you still have trouble with php5-devel.

I noticed the distfiles being mirrored very quickly when updating the  
wine and glib2 ports so I expect php5 will be fine too.

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
[prev in list] [next in list] [prev in thread] [next in thread]