Add a standard site alias '@none' [#1257760]

This patch adds an alias '@none' => array('root' => '', 'uri' => ''). Two uses for this:

1. When cdw is inside a drupal site, drush @none ... will de-select that site.

2. drush_invoke_process('@none', ... ) becomes the non-bootstrapped equivalent to drush_invoke_process('@self', ... ). For example, site-upgrade uses '@none' to insure that pm-releases operates on a non-bootstrapped site rather than the default (the d6 site being upgraded).

Comment	File	Size	Author
#1	none-alias-4.x.patch	2.91 KB	greg.1.anderson
	none-alias.patch	3.04 KB	greg.1.anderson

Comments

Comment #1

greg.1.anderson commented 23 August 2011 at 23:24

Status	File	Size
new	none-alias-4.x.patch	2.91 KB

Here is the same thing for 4.x, with an additional fix to allow drush_invoke_process('@self', ...); again.

Comment #2

moshe weitzman commented 23 August 2011 at 23:31

Seems useful to me.

Do you think these embedded calls to pm-download should use --cache by default?
Could we add this to the site alias docs?

Comment #3

greg.1.anderson commented 24 August 2011 at 00:11

Regarding docs, the alias topic just dumps examples/example.aliases.drushrc.php, which already has new docs in the above patches.

I think that the embedded call to pm-download should pass through the value of --cache. The easiest way to do this would be to add 'context' => 'DRUSH_CACHE' to the cache entry in drush_get_global_options, just like NOCOLOR does. (Of course, we would have to set the context too.)

I also think that cache should default to on always. However, shouldn't I perhaps commit #0 and #1, and handle cache changes as a separate issue? We can continue to discuss cache here if you prefer, though.

Comment #4

greg.1.anderson commented 24 August 2011 at 00:42

The wget package handler seems to cache invariantly, regardless of the setting of --cache. The git package handler creates a git reference cache if --cache is set. When pm-enable calls pm-download, it sets --cache, but this is the only place, and it seems unnecessary. If any changes are desired to the cache handling (beyond -removing- --cache from pm-enable's call to pm-download), it will take some consideration and discussion.