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

cmd/go: binary-only interacts badly with removing packages #3268

Closed
rsc opened this issue Mar 10, 2012 · 1 comment
Closed

cmd/go: binary-only interacts badly with removing packages #3268

rsc opened this issue Mar 10, 2012 · 1 comment
Milestone

Comments

@rsc
Copy link
Contributor

rsc commented Mar 10, 2012

If you remove a package directory and recompile
some other things, you might not notice that they
depend on the remove directory if the binary still
exists.  And now 'go clean -i dir' doesn't work anymore.

1) Do not allow binary-only in the current root.
2) Make go clean -i work on binary-only.
@rsc
Copy link
Contributor Author

rsc commented Mar 27, 2012

Comment 1:

This issue was closed by revision 6b09295.

Status changed to Fixed.

@rsc rsc added fixed labels Mar 27, 2012
@rsc rsc self-assigned this Mar 27, 2012
@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants