Everything is in place now. We don't use the source repository anymore 
for Phing, Propel, and Doctrine. We instead use our own mirrors.

More information on the symfony blog:

http://www.symfony-project.org/blog/2009/08/27/subversion-mirrors-for-phing-propel-and-doctrine

Fabien

--
Fabien Potencier
Sensio CEO - symfony lead developer
sensiolabs.com | symfony-project.org | fabien.potencier.org
Tél: +33 1 40 99 80 80


Dennis Benkert wrote:
> Hey Fabien,
> 
> I was aware about that. I thought that you might submit the code of the 
> externals right into the repository when creating the tag so that there 
> are no externals in tagged versions.
> 
> But anyway. We now have a solution. Thanks for putting up the mirrors so 
> quickly!
> 
> - Dennis
> 
> Fabien Potencier wrote:
>> The externals are already freezed with eitheir a tag or a specific 
>> revision. But that does not solve the problem.
>>
>> Subversion always tries to update a repo, even if you specify the 
>> revision. Sounds stupid? Yes, but this is the way it works.
>>
>> I'm quite finished with the mirrors, so expect them to be online soon.
>>
>> Fabien
>>
>> --
>> Fabien Potencier
>> Sensio CEO - symfony lead developer
>> sensiolabs.com | symfony-project.org | fabien.potencier.org
>> Tél: +33 1 40 99 80 80
>>
>>
>> Dennis Benkert wrote:
>>   
>>> I like this idea. +1 for freezed externals in symfony's tagged versions.
>>>
>>> - Dennis
>>>
>>> rooster (Russ) wrote:
>>>     
>>>> +1 I would like to see externals "frozen" in symfony tagged releases -
>>>> it can be quite disruptive when they fail :)
>>>>
>>>> Russ.
>>>>
>>>>   
>>>>       
>>>     
>>
>>   
> 
> 
> > 
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to