forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: Forrest-core (Re: mini-forrest (was Re: Recommended DTD version?))
Date Tue, 07 Dec 2004 23:11:40 GMT
Thorsten Scherler wrote:
> Ross Gardler escribió:
>>Sylvain Wallez wrote:
>>>Thorsten Scherler wrote:
>>>>In the light of cocoon writing a new core, maybe we should think about
>>>>integrating cocoon smoother into forrest. Over in lenya there is a
>>>>recent thread about cocoon versions. That made me think about how can we
>>>>keep everything as small as possible. I mean something like including
>>>>cocoon via svn:external.
>>>Sorry for the newbie question: what is "svn:external"?
>>I've never used it so am not 100% sure of its uses but from 
>> I 
>>gather "The svn:externals property contains instructions for Subversion 
>>to populate a versioned directory with one or more other checked-out 
>>Subversion working copies."
>>In other words, do a checkout of project A and automatically get 
>>relevant content from project B as well.
>>More info at
> Yes, Ross is right. 
> We (lenya) are using it to include Bitflux to the check out. That let us
> using the latest and greatest Bitflux code.

What happens with the automated "snapshots" and
with rolling a release? Does this foreign code
get included in the distribution?


View raw message