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.

Files: 

Comments

dww’s picture

Priority:Critical» Normal

It'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.

jhedstrom’s picture

Since drush plugins can be installed by drush, perhaps just add this to the project page, under an 'Installation' heading.

drush dl drupalorg_drush

That will put it in the user's .drush directory so long as it doesn't include a .module file.

dww’s picture

Except that doesn't work without a release node. :(

% drush dl drupalorg_drush
No release history was found for the requested project                 [warning]
(drupalorg_drush).
webchick’s picture

Right. ;) hence the critical.

Kristen Pol’s picture

I 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 the drush verify-makefile successfully (after running drush 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.

  1. Install drush by following the instructions on the project page or in the README.txt file.
  2. Install Drupal.org drush as follows:
    1. Grab Drupal.org drush via git, e.g.
      git clone [user]@git.drupal.org:project/drupalorg_drush.git drupalorg_drush
    2. Move the drupalorg_drush directory under [path-to-drush]/drush/commands directory.
  3. Clear the drush cache, e.g.
    drush cache-clear drush
  4. Verify that Drupal.org drush is installed by running one of the commands, e.g.
    drush verify-makefile
Kristen Pol’s picture

Title:Create a release node for Drupal.org Drush» Create a release node for Drupal.org Drush or provide documentation on usage
btopro’s picture

+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

btopro’s picture

minor 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

dnotes’s picture

(edited out the frustrated tirade I wrote because this took me so long)
Here's a patch for an INSTALL.txt file.

btopro’s picture

+1 D.O. should be all about transparency in all things.

jlyon’s picture

It seems like this should work just like Registry Rebuild. You can just drush dl registry_rebuild and it is installed in the .drush dir.

dnotes’s picture

jlyon when I try this I just get the message that no release history is found.

-enzo-’s picture

I 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.

anarcat’s picture

Status:Active» Reviewed & tested by the community

This should be a release nodes, and the install instructions should simply be:

drush dl drupalorg_drush

hefox’s picture

Ditto, release node would be useful

andrewfn’s picture

Having 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.

snapshot=68dfa3e42f1c53cef5e10f95f4dba5e4aba104b5
wget http://drupalcode.org/project/drupalorg_drush.git/snapshot/$snapshot.tar.gz -o drupalorg_drush.tar.gz
tar -xzf drupalorg_drush.tar.gz
rm drupalorg_drush.tar.gz
mv drupalorg_drush* ~/.drush/drupalorg_drush

I would value any improvements to the script that anyone can suggest.

cweagans’s picture

Being able to `drush dl drupalorg_drush` would be super helpful. Any news on having a release node? Even a snapshot release?

jhedstrom’s picture

I think dww is the only one who can make this happen as current project permissions stand.

kae76’s picture

Not 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-7957061

This is for a specific project granted but I think this would be useful for others who might end up facing similar problems.

fxi’s picture

hi 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" :

drush cc all
No path was set for including the release_info engine updatexml.                                                                                                              [error]

or with a -v :

drush cc -v
Initialized Drupal 7.24 root directory at /path/to/mysite                                                                                                                      [notice]
Initialized Drupal site default at sites/default                                                                                                                                 [notice]
No path was set for including the release_info engine updatexml.                                                                                                              [error]
Command dispatch complete               

googled a bit and got the direction but time saving tips will be greatly appreciated..

kae76’s picture

Hi fxi re your comment #20

Have you tried:

.2 To add Drupal.org drush to my commands:

cd /Applications/drush/command
git clone http://git.drupal.org/project/drupalorg_drush.git 
cd drupalorg_drush
drush cc drush
drush verify-makefile

(ref: link in comment #19)

fxi’s picture

Hi 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?

fxi’s picture

OK 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.

webchick’s picture

This 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. :\

MacMladen’s picture

Issue summary:View changes

Really, 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?

MacMladen’s picture

Man, 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?

jhedstrom’s picture

StatusFileSize
new135.98 KB
new137.95 KB

I 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:

hefox’s picture

Mentioned in IRC but should repeat here, enable "Has project releases" via the node edit form will likely fix that issue :)

jhedstrom’s picture

StatusFileSize
new45.13 KB
new29.58 KB

There is no such checkbox on the edit form. Permissions strike again?

This project:

Normal project:

jhedstrom’s picture

Version:» 7.x-1.x-dev
Status:Reviewed & tested by the community» Fixed

Hefox turned on releases, and I rolled a dev release.

drush dl drupalorg_drush

now works as expected. Sorry for the epic delays.

webchick’s picture

YES!! That's great, jhedstrom and hefox! Thanks!! :D

Status:Fixed» Closed (fixed)

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

mariacha1’s picture

Just wondering if this actually does automatically move the drupalorg_drush folder into the .drush directory for others? It's not working for me.

jhedstrom’s picture

Status:Closed (fixed)» Needs work

The 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.

jhedstrom’s picture

jhedstrom’s picture

Status:Needs work» Fixed

The issue mentioned in #34 is fixed in the latest drush.

Status:Fixed» Closed (fixed)

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