Running Drupal from CVS and OMP issues?
Kevin and crew--
At OMPCamp in Portland we started (but did not conclude) a discussion about running / installing Drupal from the CVS repositories. I was under the impression that installing Drupal from CVS made updating and patching the system significantly easier. My takeaway on the conversation was that it wasn't as great an idea as I'd been led to believe.
Can you share your thoughts more completely on this idea? Is there a price to be paid for that convenience? Is it okay for other systems, just not OMP? Did I totally misread the (brief) discussion?
Thanks!
Groups:
Login to post comments
The downside to pulling
The downside to pulling modules from CVS is they lack version numbers in the Admin Module list and update status. The version number is added to the modules .info file by the Project module when the single archive is rolled up by the project module. Looking at the screenshot from DOM, you notice there is no version number on Filefield and Imagefield.
Update Status relies on version numbers to alert you to updates. We're also starting to check version numbers as part of om_support. I'm not saying you should never use the CVS version, but if you're trying to streamline the update process you should be looking at Drush and the dev version of Plugin Manager.