I like the drupal ebuild - very clever the way it downloads all the themes and modules. However, I find that with the 4.6.0 ebuild it downloads a couple of modules which have conflicts: 1) Amazon Search conflicts Amazon Tools - both have functions called amazon_search_XXX 2) Smarty Pants conflicts Markdown Smarty - both have functions called SmartyPants I worked around this by removing Amazon Search and Smarty Pants modules (somewhat arbitrary choice). At this point I can now get into the Admin/Modules page However "Help Edit" leaves an error message at the top of the screen because it is expecting me to have run the mysql file which creates a new table. I haven't tried many of the modules, but I notice that a few have further dependencies, for example the TinyMCE module needs you to download the TinyMCE code and also to install it's mysql file I prefer to submit patches and not bugs, but not really sure what's the best thing to do here. Certainly can you please ammend the files/4.6.0/modules file and remove the files described above or else the user gets an immediate error trying to view the modules page (which is quite difficult to figure out). However, whats the next step? Should I fixup the ebuild to install all of the modules correctly, or perhaps we shouldn't install any (or hardly any) of these modules since they seem to present a potential security problem at some future point.. (installing a bunch of extra code of unknown quality...) I don't know my way around Drupal (yet), but I suggest that the module list is trimmed right back to just the most useful modules and the user is left to install any extra they need by hand...? Reproducible: Always Steps to Reproduce:
Stu's our man...
Hi, We can do that. Amazon_search and smartypants. Fixed in CVS.
