Skip to content
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

proposal: rename executable to masonry #177

Open
afeld opened this issue Jun 23, 2016 · 2 comments
Open

proposal: rename executable to masonry #177

afeld opened this issue Jun 23, 2016 · 2 comments

Comments

@afeld
Copy link
Member

afeld commented Jun 23, 2016

I don't think that name is taken by any major tool, and it's faster to type than compliance-masonry. If, however, it makes lots of tools that assume an executable of the package name harder to use, it's not worth it.

@afeld afeld changed the title rename executable to masonry proposal: rename executable to masonry Jun 23, 2016
@mogul mogul added the HighBar label Jul 8, 2016
@pburkholder
Copy link
Contributor

Or just rename the entire project to 'masonry'?

@mogul mogul added the Icebox label Jan 24, 2017
@mogul mogul removed the Icebox label Feb 2, 2017
redhatrises added a commit to redhatrises/compliance-masonry that referenced this issue Jun 8, 2018
- Create a new compliance-masonry executable for legacy uses
- New masonry.go is now the primary program naming
- Fixes opencontrol#177
redhatrises added a commit to redhatrises/compliance-masonry that referenced this issue Jun 8, 2018
- Create a new compliance-masonry executable for legacy uses
- New masonry.go is now the primary program naming
- Fixes opencontrol#177
redhatrises added a commit to redhatrises/compliance-masonry that referenced this issue Jun 8, 2018
- Create a new compliance-masonry executable for legacy uses
- New masonry.go is now the primary program naming
- Fixes opencontrol#177
@shawndwells
Copy link
Member

@afeld @pburkholder the CLI was renamed through #291.

Should we also rename the repo? GitHub automatically takes care of redirects, so docs/presentations/etc would automatically get forwarded.

@shawndwells shawndwells reopened this Jun 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants