El sáb, 04-03-2006 a las 00:17 +0100, Michael Wechner escribió:
> Michael Wechner wrote:
> 
> > Thorsten Scherler wrote:
> >
> >> El vie, 03-03-2006 a las 14:14 +0100, Michael Wechner escribió:
> >>  
> >>
> >>> Andreas Hartmann wrote:
> >>>
> >>>   
> >>>
> >>>> Andreas Hartmann wrote:
> >>>>
> >>>> [...]
> >>>>
> >>>>     
> >>>>
> >>>>>> It's true that because Lenya and Cocoon are in the same 
> >>>>>> repository, you
> >>>>>> could say that the LCR should be equal. But you would have to get 
> >>>>>> the
> >>>>>> right revision manually.
> >>>>>>         
> >>>>>
> >>>>> We would need something like symbolic links in the SVN repository, so
> >>>>> that the same version is checked out for Lenya and Cocoon ...
> >>>>> I'll try to find out if this problem can be solved.
> >>>>>       
> >>>>
> >>>> It seems that we have to use explicit revision numbers.
> >>>> Maybe we should add an Ant target to update the externals
> >>>> declaration to make it easier to "update" to a new Cocoon
> >>>> revision.
> >>>>     
> >>>
> >>> Although I understand the concerns of Josias, I think for the moment 
> >>> we should
> >>> just to svn:external which is better than the current situation ;-)
> >>>   
> >>
> >>
> >> Actually we already agreed because we want to develope trunk with head
> >> of cocoon-2.1.x.
> >>  
> >>
> >
> > ok, I will add it right know within src/cocoon_2_1_x
> 
> 
> I just realize that this is not such a good idea, because if one
> does svn st or svn up one gets all the externals listed of Cocoon and
> can easily miss something within the src dir of Lenya.
> Also I think one should see clearly what is external, etc., so will
> move it into
> 
> externals/cocoon_2_1_x

why not vendors/cocoon_2_1_x?

> 
> maybe we could also move bxe and kupu in there.

vendors/bxe
vendors/kupu
...

> 
> WDYT?

+1 

all external vendors should go to the vendors dir. ;)

salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to