Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
Andreas Hartmann wrote:
Hi Lenya devs,
currently, the build scripts (build.sh, build.bat) point to
externals/cocoon_2_1_x/lib/endorsed.
IIUC 1.4 RC 1 shall be compiled against Cocoon 2.1.10
(please correct me if I'm wrong).
makes sense, unless the cocoon crowd is getting 2.1.11 out within the
next 2 weeks (2.1.11-dev has gotten a lot more testing lately than
2.1.10, since we've all been using it...)
IMO we shouldn't wait. Maybe we can do another release candidate
when 2.1.11 is released.
agreed.
I'd suggest that we remove the externals declaration to avoid
confusion and to keep the tagged version smaller.
you mean require users to download 2.1.10 separately? i don't like that...
How should we handle it? Should we include the source tree?
My first thought was to change the svn:externals to the tagged
version of 2.1.10. But this version includes svn:externals for
the blocks, so that wouldn't make sense.
i don't understand... what's the problem with including an external to
the 2.1.10 tagged branch? why should we care about any externals in cocoon?
How should we reference the endorsed libraries directory when
we build against a separate Cocoon? Do we have to require the
user to edit the build scripts?
that seems to be the standard procedure. we should extend
configure.[sh|bat] to ask for the path...
Good idea.
yes, *if* we don't include the cocoon source, but i've gotten used to
that luxury over the last year and would hate to see it go...
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
Kurt is up in Heaven now.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
