Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Right now, the only way to get this module is with a git clone.
We should provide at least a dev tarball on the front page. Preferably a stable release.
Comment | File | Size | Author |
---|---|---|---|
#29 | Selection_016.jpg | 29.58 KB | jhedstrom |
#29 | Selection_015.jpg | 45.13 KB | jhedstrom |
#9 | drupalorg_drush-add_install_file-1432296-9.patch | 442 bytes | dnotes |
Comments
Comment #1
dwwIt's not a module. ;) It's a drush plugin. We really need #322626: META: Package and version non-modules for download. :/
Also, I'm downgrading this, since I don't see how this is blocking progress on anything. I suppose webchick's going to argue that we want to have this distro stuff available to "the masses". I disagree. Distro maintainers aren't just anybody. We have to assume a certain level. "Jump right in and contribute" doesn't work here. You have to already be pretty advanced to actually maintain a distro. And you have to know how to use Git.
Comment #2
jhedstromSince drush plugins can be installed by drush, perhaps just add this to the project page, under an 'Installation' heading.
That will put it in the user's .drush directory so long as it doesn't include a .module file.
Comment #3
dwwExcept that doesn't work without a release node. :(
Comment #4
webchickRight. ;) hence the critical.
Comment #5
Kristen PolI am creating an installation profile (and distribution) for my new multilingual book so the reader can get up-and-running quickly with a demo site.
It wasn't entirely obvious to me what I was supposed to do to get the Drupal.org drush plugin installed as I hadn't installed other plugins for drush before. Since there was no release, then I assumed I needed to get Drupal.org drush via git, which I did. Then I just put the directory under
drush/commands
. It appears to have worked as now I can run thedrush verify-makefile
successfully (after runningdrush cache-clear drush
).Anyway, all of this was after some head-scratching and going back-and-forth between doc pages, etc. I didn't see any obvious documentation on this. I'd be happy to add some myself but @dww comment makes it sound like this isn't for mass consumption. So...
1) Is there documentation that explains how to install/use Drupal.org drush?
and, if not,
2) Do we want this? And, if so, where?
My steps are as follows. These could be used as a starting point for the documentation if it is desired/needed.
drupalorg_drush
directory under[path-to-drush]/drush/commands
directory.Comment #6
Kristen PolComment #7
btopro CreditAttribution: btopro commented+1 for release node; this took me awhile to hunt down this thread which I still can't get installed cause my osx setup is less then ideal
Comment #8
btopro CreditAttribution: btopro commentedminor installation note; if using the pear method of drush install your location to add this package in OSX will most likely be /usr/lib/php/drush/commands
Comment #9
dnotes CreditAttribution: dnotes commented(edited out the frustrated tirade I wrote because this took me so long)
Here's a patch for an INSTALL.txt file.
Comment #10
btopro CreditAttribution: btopro commented+1 D.O. should be all about transparency in all things.
Comment #11
jlyon CreditAttribution: jlyon commentedIt seems like this should work just like Registry Rebuild. You can just
drush dl registry_rebuild
and it is installed in the.drush
dir.Comment #12
dnotes CreditAttribution: dnotes commentedjlyon when I try this I just get the message that no release history is found.
Comment #13
-enzo- CreditAttribution: -enzo- commentedI still got the message same message "No release history was found for the requested project (drupalorg_drush). [warning]". I have to had to follow the patch #9 and works.
Comment #14
anarcat CreditAttribution: anarcat commentedThis should be a release nodes, and the install instructions should simply be:
drush dl drupalorg_drush
Comment #15
hefox CreditAttribution: hefox commentedDitto, release node would be useful
Comment #16
andrewfn CreditAttribution: andrewfn commentedHaving spend a frustrating hour and a half trying to install this plugin, I thought it might be useful to someone if I posted my bash script here. The value of snapshot is taken from this page http://drupalcode.org/project/drupalorg_drush.git and determines which 'release' is installed.
I would value any improvements to the script that anyone can suggest.
Comment #17
cweagansBeing able to `drush dl drupalorg_drush` would be super helpful. Any news on having a release node? Even a snapshot release?
Comment #18
jhedstromI think dww is the only one who can make this happen as current project permissions stand.
Comment #19
kae76 CreditAttribution: kae76 commentedNot sure if useful here, if anyone knows where I could put this I would be grateful of advices.
I had to grab
drupalorg_drush
and found all the info a bit scattered across interwebs, so I documented here: https://drupal.org/comment/7957061#comment-7957061This is for a specific project granted but I think this would be useful for others who might end up facing similar problems.
Comment #20
fxi CreditAttribution: fxi commentedhi guys
tried all the methods you mentioned: git clone, `drush dl drupalorg_drush` , and #16 script , on each method i get the same result: drush gets defunct givin this error for any command, including a simple "drush cc all" :
or with a -v :
googled a bit and got the direction but time saving tips will be greatly appreciated..
Comment #21
kae76 CreditAttribution: kae76 commentedHi fxi re your comment #20
Have you tried:
.2 To add Drupal.org drush to my commands:
(ref: link in comment #19)
Comment #22
fxi CreditAttribution: fxi commentedHi kae76, Thanx for answering.
Yes I have tried that, with two variations adjusting to my system:
1 - My path is /usr/share/drush/commands since I'm using ubuntu LAMP
2 - I dont have a fully functional drush environment at that path, so I cd'd to the path of one of my virtual hosts directory and ran 'drush cc drush' .
Any direction?
Comment #23
fxi CreditAttribution: fxi commentedOK my bad. My drush here was less than 5, missed the specified prerequisites.
Upgraded as described here : https://drupal.org/node/1248790 , and all is up and running. Maybe it's a good thing to check the version as part of the install.
Thanx for your help.
Comment #24
webchickThis is a getting to be a bit silly.
Now the official instructions at https://drupal.org/developing/distributions/drupalorg link off to an arbitrary comment in this issue for installation instructions, simply because
drush dl drupalorg_drush
doesn't work. :\Comment #25
MacMladen CreditAttribution: MacMladen commentedReally, this is unnecessary complication, this module is referred to on number of places and yet simple
drush dl drupalorg_drush
is failing.I agree it should operate as Registry Rebuild is working now
drush dl registry_rebuild
by directly going into drush commands and it is not too hard to do so, either.So why is it such a problem when (nearly) everyone thinks it should be that way? What is the reason not to do so?
Comment #26
MacMladen CreditAttribution: MacMladen commentedMan, even wechick told you two years ago and tells you so again: yes it is silly as it is very important, just unnecesary annoying (not that any developer will not be able to figure out).
Can a simple please be of any assistance?
Comment #27
jhedstromI now have all permissions on this project, but however it was moved from the d.o. 6.x site to 7.x, it lost its ability to support releases?
Normal project:
This project:
Comment #28
hefox CreditAttribution: hefox commentedMentioned in IRC but should repeat here, enable "Has project releases" via the node edit form will likely fix that issue :)
Comment #29
jhedstromThere is no such checkbox on the edit form. Permissions strike again?
This project:
Normal project:
Comment #30
jhedstromHefox turned on releases, and I rolled a dev release.
drush dl drupalorg_drush
now works as expected. Sorry for the epic delays.
Comment #31
webchickYES!! That's great, jhedstrom and hefox! Thanks!! :D
Comment #33
mariacha1 CreditAttribution: mariacha1 commentedJust wondering if this actually does automatically move the drupalorg_drush folder into the .drush directory for others? It's not working for me.
Comment #34
jhedstromThe reason this still isn't working is that this project isn't setup as a module. Rather it is described as
project_drupalorg
in the release xml.Does anybody know how to change that?
Drush is explicitly only moving projects identified as modules that have no
.module
file into the.drush
directory.Comment #35
jhedstromRelated drush issue: https://github.com/drush-ops/drush/pull/974
Comment #36
jhedstromThe issue mentioned in #34 is fixed in the latest drush.