First of all, great module.
I have managed to successfully install drush on my local windows box. For the most part i have everything working fine.
i can use drush dl , most of the other drush commands.
However i want to download modules in to a subdir of my modules folder of my installation so i tried the following -
drush dl modulename --destination=www/sites/all/modules/contrib.
I have also tried various other combinations from different folder levels + adding the full path in the --destination parameter as such -
drush dl modulename --destination=C:\project\www\sites\all\modules\contrib.
All of the above return the error saying - The destination directory 1/ does not appear to exist.
Can anyone give any pointers to correctly using the --destination on a windows machine?
thanks.
Comments
Comment #1
greg.1.anderson commentedAre you using drush HEAD? This might be a duplicate of #636738: tar command doesn't work on windows or solaris, which was only recently fixed and committed.
Comment #2
tayzlor commented@greg.1.anderson Im only using the latest release, not HEAD, but Drush is able to unzip the package that comes down easy enough, i just cant specify which folder in my directory i want the download to come into if that helps?
Comment #3
greg.1.anderson commentedI didn't look into your bug, and don't have time to right now. It would be helpful if you checked out drush from CVS (see the "cvs instructions" tab on the drush project home page) and try to reproduce the problem. It might already be fixed, or this might be something else.
Comment #4
tayzlor commentedchecked out HEAD from CVS, tested this functionality and the problem still exists.
Comment #5
moshe weitzman commentedpls try with head again. we improved tar functionality
Comment #6
greg.1.anderson commentedNo feedback. Please re-open with more information if needed.
Comment #7
azovsky commentedHi,
Im have this error.
BUT! It works (without --destination):
Using:
In what may be the problem?
Comment #8
moshe weitzman commentedcould someone on windows try to reproduce this and find a fix?
Comment #9
greg.1.anderson commentedCombining Windows path issues in #766080: Windows support for drush: escaping the path to drush in backend invoke and elsewhere.