这是indexloc提供的服务,不要输入任何密码
Skip to content

[flutter_tools] remove execute permissions on shared.sh, and move off path #58267

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 3 commits into from
May 29, 2020

Conversation

christopherfujino
Copy link
Contributor

Because flutter/bin/shared.sh was originally created by renaming flutter/bin/flutter, it inherited execute permissions and the shebang at the top. As it is only being sourced for function definitions, it needs neither of these, so this PR removes them. It also moves them from flutter/bin/shared.sh -> flutter/bin/internal/shared.sh so that it doesn't appear on the path if the user has added flutter/bin to their path (it would have been a no-op if they executed it previously).

@christopherfujino christopherfujino changed the title remove execute permissions on shared.sh, and move off path [flutter_tools] remove execute permissions on shared.sh, and move off path May 29, 2020
Copy link
Contributor

@gspencergoog gspencergoog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

32384589-a60f0e74-c078-11e7-9bc1-e5b5287aea9d

@christopherfujino
Copy link
Contributor Author

I put back the shebang, as it made the license check in the analyze-linux sad.

@fluttergithubbot fluttergithubbot merged commit 30fed04 into flutter:master May 29, 2020
@christopherfujino christopherfujino deleted the update-bash branch May 29, 2020 23:40
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants