Druplets, not droplets ;)<br><br><div><span class="gmail_quote">2006/8/8, Chris Johnson <<a href="mailto:chris@tinpixel.com">chris@tinpixel.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Adrian Rossouw wrote:<br>> <a href="http://drupal.org/node/77549">http://drupal.org/node/77549</a><br>><br>> I am not going to re-hash everything I said there, but I need to say<br>> that install profiles as they are now are not really adequate
<br>> for many of the things we hope to accomplish with them.<br>><br>> I have been building install profiles in one manner or another for 2<br>> years now, and that patch is part of what I found were the base
<br>> requirements of making install profiles work for us, and very likely<br>> anybody who runs more than 1 site on an install.<br><br>This looks good to me. We have a need for installing multi-site distributions<br>
where some instances have differing sets of modules and themes available from<br>other instances. Without this patch or install config data in its own<br>directory, there are problems with that kind of mass hosting.<br><br>
Can we use a different name than "install profile" to avoid confusion with<br>other uses of the word "profile"? How about distributions and the files can<br>be called "distfiles" (Unix precedent from rdist command) or something. Or we
<br>could be like Python and invent new names and call them "drops" or "droplets"<br>or something. :-)<br><br>..chrisxj<br></blockquote></div><br>