On 13-Jul-06, at 11:28 AM, Dries Buytaert wrote:
On 13 Jul 2006, at 17:19, Earl Dunovant 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?
Earlier this week I explained why I do not intend to remove core modules, except maybe for the archive.module. The install system doesn't change that fact.
Should I move the archive module to contrib?
Or get a maintainer and replace it with that CodeMonkeyX updated one. I have no problem with archive-functionality in core...I have a problem with a *crappy* archive module in core. (to which, of course, the answer is -- supply patches) -- Boris