I
don't think so. I think it's far more promising to look at it as an opportunity
for groups of modules to be bundled together in a collection, along with a
'profile' that does the setup and integration work for them.
You'd
copy Drupal to your server, then copy the profile on top of it, then run
install.php.
--Jeff
On 7/13/06, Dries
Buytaert <dries.buytaert@gmail.com> wrote:
But
it begs the question: how are we going to handle
install
profiles? Where and how to maintain
them? Should we have one or
more profiles in core?
If you have profiles is core, does that kill the idea of Drupal
developing into a set of APIs and cutting back on core modules?