-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Remove Finder+Launcher. Use DrupalFinder #2749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,115 +1,4 @@ | ||
| #!/usr/bin/env php | ||
| <?php | ||
|
|
||
| /** | ||
| * This is the Drush "finder" script, which is one part of the | ||
| * Drush dispatching chain. This is the script that | ||
| * should appear in your global $PATH, or, if using Composer | ||
| * (as usually the case), will be found in your vendor/bin directory. | ||
| * | ||
| * | ||
| * - Never copy this script to your site root. Copy examples/drush instead. | ||
| * | ||
| * - Never copy this script to a directory other than its install directory. | ||
| * Symlink to it instead. | ||
| * | ||
| * | ||
| * OVERVIEW OF DRUSH FINDER / WRAPPER / LAUNCHER SCRIPTS | ||
| * | ||
| * When the user types "drush", up to three scripts might be | ||
| * involved in the initial launch: | ||
| * | ||
| * "drush finder" -> "drush wrapper" -> "drush launcher". | ||
| * | ||
| * Brief description of each: | ||
| * | ||
| * - Drush finder: Finds the right Drush script and calls it. | ||
| * - Drush wrapper: Contains user customizations to options. | ||
| * - Drush launcher: Excutes drush.php. | ||
| * | ||
| * A full explanation of each script follows. | ||
| * | ||
| * | ||
| * DRUSH FINDER | ||
| * | ||
| * - The "drush" script on the user's global $PATH | ||
| * - It's goal is to find the correct site-local Drush to run. | ||
| * | ||
| * The Drush finder will locate the correct site-local Drush to use | ||
| * by examining: | ||
| * | ||
| * a) The --root option | ||
| * b) The site set via `drush site set` in the current terminal | ||
| * c) The cwd | ||
| * | ||
| * If no site-local Drush is found, then the global Drush will be | ||
| * used. The Drush finder assumes that the global Drush is the | ||
| * "Drush launcher" found in the same directory as the Drush finder itself. | ||
| * | ||
| * If a site-local Drush is found, then the Drush finder will call | ||
| * either the "Drush wrapper", if it exists, or the "Drush launcher" if | ||
| * there is no wrapper script. | ||
| * | ||
| * | ||
| * DRUSH WRAPPER | ||
| * | ||
| * - The drush.wrapper script that the user optionally copies and edits. | ||
| * - Its goal is to allow the user to add options when --local is in use | ||
| * | ||
| * The Drush "wrapper" is found at examples/drush.wrapper, and may optionally | ||
| * be copied to __ROOT__ by the user. It may be named either | ||
| * "drush" or "drush.wrapper". It will call the "Drush launcher" | ||
| * for the same site that it is located in. It adds the --local flag; the | ||
| * user is encouraged to add other options to the "Drush wrapper", e.g. to set | ||
| * the location where aliases and global commandfiles can be found. | ||
| * The Drush "finder" script always calls the "Drush wrapper" if it exists; | ||
| * however, if the user does not want to customize the early options of | ||
| * the site-local Drush (site-alias locations, etc.), then the wrapper does not | ||
| * need to be used. | ||
| * | ||
| * | ||
| * DRUSH LAUNCHER | ||
| * | ||
| * - The "drush.launcher" script in vendor/bin | ||
| * - The bash script formerly called "drush" | ||
| * | ||
| * The "Drush launcher" is the traditional script that identifies PHP and | ||
| * sets up to call drush.php. It is called by the "Drush wrapper", or | ||
| * directly by the "Drush launcher" if there is no "Drush wrapper" in use. | ||
| * | ||
| * | ||
| * LOCATIONS FOR THESE SCRIPTS | ||
| * | ||
| * "Drush finder" : __ROOT__/vendor/bin/drush (composer install) | ||
| * __DRUSH__/drush (source) | ||
| * | ||
| * "Drush wrapper" : __ROOT__/drush (copied by user) | ||
| * __DRUSH__/examples/drush.wrapper (source) | ||
| * | ||
| * "Drush launcher" : __ROOT__/vendor/bin/drush.launcher (composer install) | ||
| * __DRUSH__/drush.launcher (source) | ||
| * | ||
| * | ||
| * BACKEND CALL DISPATCHING | ||
| * | ||
| * Backend calls are typically set up to call the "drush" script in the $PATH, | ||
| * or perhaps some might call __ROOT__/vendor/bin/drush directly, by way | ||
| * of the "drush-script" element in a site alias. In either event, this is | ||
| * the "drush finder" script. | ||
| * | ||
| * The backend call will always set --root. The "Drush finder" script | ||
| * always favors the site-local Drush stored with the site indicated by the | ||
| * --root option, if it exists. If there is no site-local Drush, then the | ||
| * "Drush finder" will behave as usual (i.e., it will end up calling the | ||
| * "Drush launcher" located next to it). | ||
| * | ||
| * This should always get you the correct "Drush" for local and remote calls. | ||
| * Note that it is also okay for aliases to specify a path directly to | ||
| * drush.launcher, in instances where it is known that a recent version of | ||
| * Drush is installed on the remote end. | ||
| */ | ||
|
|
||
| if (!function_exists("drush_startup")) { | ||
| include __DIR__ . '/includes/startup.inc'; | ||
| } | ||
| drush_startup($argv); | ||
| require __DIR__ . '/drush.php'; |
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,3 @@ | ||
| #!/usr/bin/env php | ||
| <?php | ||
| /** | ||
| * @file | ||
|
|
||
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened to
php-options? Don't we still need this in backend invoke?