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.

Sign up for GitHub

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

Jump to bottom

Perhaps rename the script from release to e.g. gap-pkg-release, to make it "installable" into PATH? #60

Closed
fingolfin opened this issue Dec 4, 2018 · 1 comment
Closed

Perhaps rename the script from release to e.g. gap-pkg-release, to make it "installable" into PATH? #60

fingolfin opened this issue Dec 4, 2018 · 1 comment

Comments

@fingolfin
Copy link
Member

fingolfin commented Dec 4, 2018 •
edited
Loading

Name ideas:

  • gap-pkg-release
  • release-gap-pkg
  • gap-package-release
  • release-gap-package
  • ... ?

To make the transition easy, I'd keep a symlink release -> NEW_NAME in the repository. This way, existing user's won't even notice.
@olexandr-konovalov
Copy link
Member

Almost my setup:) I have a symlink /usr/local/bin/gap-package-release -> /Users/alexk/GITREPS/ReleaseTools/release.

fingolfin added a commit that referenced this issue Feb 12, 2020
@fingolfin
Rename release -> release-gap-package
a50dd79 
Also add a symlink `release` to the new name for backwards compatibility.

Resolves #60
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fingolfin @olexandr-konovalov