drush dl moduleName assumes the download is coming from drupal.org. The url to the xml release information is hard coded to be drupal.org. How about a command line option to override that. To say, point it to a feature server or some other location supplying the proper xml information.

Comments

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Postponed (maintainer needs more info)

features module has drush integration. lets start there.

moshe weitzman’s picture

moshe weitzman commented

I should clarify - i want a lifecycle plan from the features folks about what drush functionality is needed from the core drush commands. it might make sense to do what you describe for dl command then let enable/disable commands do their thing. and after that you use feature specific commands for revert and stuff?

moshe weitzman’s picture

moshe weitzman commented
Status: Postponed (maintainer needs more info) » Active
mfer’s picture

mfer commented

I would expect the drush core commands to just treat them like any other module/theme. So "drush dl" would just download them. Anything specific to features should be in features.

A second use case is a company has company specific module(s) or theme(s) that aren't on drupal.org. These modules could be custom to specific internals in the company or a theme that has proprietary company images in it. They have a place providing the proper xml and want to use drush to download them to the site they are working on.

Ideally, I'd just like a command line option to switch to a different server.

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Fixed

Committed a --source option where one can specify a URL.

Status: Fixed » Closed (fixed)

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