Thorsten Scherler wrote:
Anyway I thought about the whole cocoon stuff a bit and asked myself
whether it makes sense to ship WITHOUT cocoon. We only recommend a
certain version/revision number.
Meaning the user would have to grep a version of cocoon himself. Would
certainly slim down the release (~100mb!).
not a problem nowadays. our users are prospective server operators, so
bandwidth should not be an issue. if anyone can demonstrate that 100
megs of download is too much for them, i'll happily prepare a stack of
3½" floppies and mail them out. or maybe fax-on-demand? ;)
sure it would be nice to separate lenya from cocoon some way, but i fear
cocoon is really hard to install from scratch when you need to put a
third party package into it (i once tried it to deploy eXist inside it,
and failed horribly). so i think our integration is really a huge
benefit, and lowers the entrance barrier significantly. people are
downloading 90 megs of openoffice without blinking, and here we are
talking about a heavyweight server application.
while we're talking about distribution, did i say before i see no real
reason to provide binaries? imho, users should compile the stuff
themselves.
imho we should also encourage users to track svn (the 2.0 branch) rather
than download packages. others have brought forth convincing arguments
that packages are a must, and i agree.
but i think serious users should prefer svn for easier deployment of
bugfixes and patches (and a way to safely downgrade if necessary), and
we should mention that in our release notes. wdyt?
--
Jörn Nettingsmeier
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
