Note on updating modules in Agaric subversion repository
svn commit -m "replaced nodefamily-5.x-1.1 with nodefamily-5.x-1.2, a module upgrade. Since our module setup has module upgrades going into a wholly new directory, it may be particularly importont to 'Submit' the modules page after upgrading... as well as running update.php of course. It's also very important of course to delete the older version of the module, since the names won't conflict and remind you."
UPDATE: running update.php seems to find the upgraded module quite well.
svn commit -m "replaced nodefamily-5.x-1.1 with nodefamily-5.x-1.2, a module upgrade. Since our module setup has module upgrades going into a wholly new directory, it may be particularly importont to 'Submit' the modules page after upgrading... as well as running update.php of course. It's also very important of course to delete the older version of the module, since the names won't conflict and remind you."
UPDATE: running update.php seems to find the upgraded module quite well.
More like this
- Making a new release for your updated Drupal module
- See what Subversion repository you are drawing from with vi .svn/entries
- Properly installing Subversion on Apache2 with SSL
- Settings for sets of sites: Putting Drush configuration into your project repository
- Agaric's SVN repository structure for site maintenance and web development


Comments
Post new comment