I sent this mail originally as a followup to #668065, but, as Daniel says, it's more pertinent to this bug. Maybe the README should be changed to reflect this? (at some point it will be useful for users to migrate to Drupal 8)
> I've been looking at the issue of installing both drupal6 and drupal7 > packages simultaneously during migration (e.g. to migrate one site at a > time if there are several sites) > > The only obvious issue that sticks out is that both new and old packages > suggest the same location for locally installed modules and themes, > /usr/local/share/drupal > > I've opened a bug about this here: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685333 > > Given that upgrades are likely to be slow and painful, co-installation > of both packages should be as easy as possible Umh... I don't know where is that suggestion, but it has never bit me - and I am currently halfway through my transition of several tens of sites in the same server. Packaged modules and themes (i.e. using dh-make-drupal) go to /usr/share/drupal6 and /usr/share/drupal7, and non-packaged ones go usually to /etc/drupal/6/sites/all and /etc/drupal/7/sites/all (or a specific site, of course). Upgrades are sometimes painful, yes, but due to issues in upgrading the specific themes and modules used, not due to them not being coinstallable. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
