Thorsten Scherler wrote:
El jue, 02-03-2006 a las 11:18 +0100, Michael Wechner escribió:
Andreas Hartmann wrote:
But that's probably because I work with Cocoon every day.
I would say so ;-)
With unfamiliar apps, I'd look for a GUI configuration option,
and if I don't find one, I'd ask on the mailing list / support.
1) Download Lenya
2) How do I build this thing and what do I need to configure ...
so my suggestion would be, let's do it the Apache httpd way ...
./configure(.sh) (interactively asking about important stuff, but it
could be optional for devs)
./build(.sh)
./startup(.sh)
WDYT?
whereas the configure script could generate the
local.* files at the right places, so everyone will be happy ...
That sounds reasonable.
let me make a first simple implementation which will overwrite
local.build.properties
¿? Why want you *override* local.build.properties? That will cause
*many* confusion. If you mean will create a l.b.p. then yes, but
overriding -1 (way too much verbose magic).
because most people already have a l.b.p!
So the configure needs to ask, shall it overwritten!
and then we can go from there and move the
stuff to local.* files and various locations without anyone noticing
except the devs.
I think we should focus on the
./configure(.sh) which would
a) create l.b.p
a I have checked-in a first version, which doesn't do much,
but should show how it can be done. Will work some more on it
this afternoon
b) create local.*.xconf
this can be done parallel or in a second step.
Please be aware that there are global parameters and
publication specific parameters. Not sure how these should
be integrated into the global config process.
Michi
Sure first we need to test local.*.xconf. ;)
salu2
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
