something is going on over there
When I want to install a new site on my laptop I do the following
Writing an article without pointer is pointless. So here is a start.
Version dependencies are described here http://www.debian.org/doc/debian-policy/ch-relationships.html
For a functional dependency specification (Nix and NixOS) see
I still forget how to do the database and user creation and drop goes. So why not make a note.
Creating
create database test;
create user 'test' identified by 'pwtest';
grant all on test.* to 'test'@'localhost' identified by 'pwtest';
Cleaning up
drop user test;
drop database;
Yeah ... call me stupid ;-)
Apart from security risk i think it would be great to have drupal install modules needed for a profile. For a commandline solution provided by drush the advantages are great.
Combining 'project provides' and clean dependency checks multi site users would get rid of the burden to get modules in place before installing.
When uninstalling modules the code uses a simple foreach to call drupal_uninstall_module.
My guess is that this should be in TSL order. And it will be easy to implement when we have the dependency graph of the modules to uninstall.
Question remains whether dependent modules should be uninstalled together. That is without the user selecting what modules to uninstall.
It's quite neat using drush to install ubercart. Here is what I did.
Preparation
Installing
Using drush with a strict server design makes my drupal maintence much more relaxed. I have this tiny script as a runner for drush.
$ cat drush
# drush pm install ubercart
My drush patch for a module manager makes it more easier to SEE what's installed.
listing# drush mm list
imagary# drush mm dot | dot -T png -o ~/graph.png
shows a module in error. (I deleted workflow_ng) scroll to the right for red
drush pm install token workflow_ng tapir ubrowser cck imagefield imagecache google_analytics ubercart