Hi, thanks for all of the hard work putting the drush_extras stuff back into drush. I'm hoping the cvs stuff will be moved back as well? It would be a great boon for sites wanting to do large updates across multiple sites.

Comments

moshe weitzman’s picture

Status: Active » Fixed

pm commands will move very soon.

chrisschaub’s picture

Thanks Moshe, great stuff. I'll definitely help test it out.

webchick’s picture

Does this mean that it'll be possible to check out an initial copy of Drupal core from CVS with Drush?

That's the one feature I'm sorely missing right now. :(

owen barton’s picture

Title: cvs back into core drush as well? » Move PM commands and CVS support to drush core
Assigned: Unassigned » owen barton
Category: feature » task
Status: Fixed » Needs work

I was working on moving the "PM" commands from extras to core today, and have them pretty much working. If folks want to help out, please test and review #415108: Conditional include API which should really go in first. I'll reopen this issue as a placeholder.

@webchick - yes, drush will download drupal core with you, either via wget or CVS if you have drush_extras available - it will also download themes, translations and install profiles too. At least, the last working version did, but things are moving pretty fast so I can't say for sure about HEAD (...one day we'll have tests hay) if it isn't right now you could always copy the pm.cvs.drush.inc from extras to the core directory and that should work just as well.

moshe weitzman’s picture

great news ... feel free to move dl command and associated helper functions into your pm file.

dugh’s picture

subscribe

timmillwood’s picture

Sounds good, I rolled my own script to do it, (see http://millwoodonline.co.uk/streamline-drupal-cvs-checkout) but if Drush could do it, that would be better.

owen barton’s picture

Status: Needs work » Fixed

Committed a first pass at these. Still need to do some refinement to get the engine help and options working correctly, and to split out some of the commands into their own files, but it should all be pretty straightforward now. Note that the --handler parameter is now --package-handler.

moshe weitzman’s picture

Status: Fixed » Needs work

pm info command gives Fatal error: Call to undefined function pm_get_project_info(). i think we just need a drush_include() call.

dl command is duplicated with pm_dl(). same for wget. seems like the ones in core can be dropped. use core dl's help and examples though.

owen barton’s picture

Fixed those 2 issues and another one with refresh. I am sure there are some more in there to discover though, once we start using it in earnest!

moshe weitzman’s picture

Minor bug in disable command? See below.

~/htd/pr6og$ drush disable activity
The following modules will be disabled: activity
Do you really want to continue? (y/n): y
Activity was disabled successfully.                                                                                             [ok]
warning: array_search(): Wrong datatype for second argument in /Users/mw/contributions/modules/drush/commands/pm/pm.drush.inc on[warning]
line 254.

Also, status modules command can't be run because we execute status command instead. I think we said that this is a known issue and we have to rename status modules.

Update bug? See below:

warning: Missing argument 1 for version_control_skip_backup(), called in                                                        [warning]
/Users/mw/contributions/modules/drush/commands/pm/update.inc on line 118 and defined in
/Users/mw/contributions/modules/drush/commands/pm/version_control/svn.inc on line 40.
warning: mkdir(): File exists in /Users/mw/contributions/modules/drush/includes/drush.inc on line 248.                          [warning]
warning: mkdir(): File exists in /Users/mw/contributions/modules/drush/includes/drush.inc on line 248.                          [warning]
moshe weitzman’s picture

Category: task » bug
Status: Needs work » Active
moshe weitzman’s picture

Status: Active » Fixed

Both issues have been resolved. First was a problem with a .info that I had enabled.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.