Don, to be clear, I was specifically responding to Lamar's
questions about how much to automate and what kinds of
defaults to set. I could still very well be wrong here, but I'm
guessing that you'd want to err on the side of enabling flexibility
for the typical OpenACS developer's RPM's while erring on the
side of ease-of-use for, say a dotLRN install conducted by
somebody who has no clue what values to set for the various
parameters. I don't know if this makes a practical difference in
how the RPMs are put together, but at the very least we should
consider the various use cases and look for discrepancies.
I didn't mean to imply that ease of installation is not a goal or
was not achieved with the developer-centric RPMs.
