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

Feature: add option to not rebuild with newer toolchain #173

Open
yukita443 opened this issue Sep 26, 2024 · 2 comments
Open

Feature: add option to not rebuild with newer toolchain #173

yukita443 opened this issue Sep 26, 2024 · 2 comments

Comments

@yukita443
Copy link

yukita443 commented Sep 26, 2024

Is your feature request related to a problem?

An option to prevent unintended rebuilds caused by toolchain updates would be useful, especially if the user has a large number of packages installed.

Describe the solution you'd like

Adding an option like gup update --ignore-go-update

Describe alternatives you've considered

Installing a binary per go toolchains installed by asdf.

Additional context

#154

@nao1215
Copy link
Owner

nao1215 commented Sep 26, 2024

@yukita443
Thank you for the suggestion of a new feature !!
I couldn't fully understand the use case, so I have a few questions.

Here is the use case I imagined:

  • You are developing multiple projects, each using a different Go version.
  • When you run go generate ./... for a project, you want to match the "Go version for the project" with the "Go version used to build the binaries under $GOPATH/bin."

Is this the situation you are referring to? I personally think it's fine to always use the latest Go version, so I’m not quite sure I understand your ideal situation.

Also, does the --ignore-go-update option skip the update only when the Go toolchain is updated? For example, if the toolchain becomes outdated, will gup still skip the update? Which of these behaviors is the feature you are requesting?

@nao1215 nao1215 reopened this Nov 3, 2024
@nao1215
Copy link
Owner

nao1215 commented Nov 3, 2024

@yukita443
Don't close without any explanation, please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants