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

Rebuild source directories added to the sandbox #1105

Closed
tibbe opened this issue Nov 8, 2012 · 7 comments
Closed

Rebuild source directories added to the sandbox #1105

tibbe opened this issue Nov 8, 2012 · 7 comments
Assignees

Comments

@tibbe
Copy link
Member

tibbe commented Nov 8, 2012

Source directories added to the sandbox using cabal sandbox add-source should be rebuilt, if needed, by e.g. cabal build.

@ghost ghost assigned 23Skidoo Nov 8, 2012
@23Skidoo
Copy link
Member

I think that it should be also possible to disable this behaviour. For example, when working on Cabal, I only run cabal-dev install Cabal/ cabal-install/ when I have changed something in the Cabal lib; usually cabal-dev install cabal-install/ is sufficient.

@23Skidoo
Copy link
Member

#1118 contains an initial implementation.

@tibbe
Copy link
Member Author

tibbe commented Nov 16, 2012

I think that it should be also possible to disable this behaviour. For example, when working on Cabal, I only run cabal-dev install Cabal/ cabal-install/ when I have changed something in the Cabal lib; usually cabal-dev install cabal-install/ is sufficient.

I think this is better solved by having minimal rebuilds, instead of forcing the user to think about what needs rebuilding.

@23Skidoo
Copy link
Member

I think this is better solved by having minimal rebuilds, instead of forcing the user to think about what needs rebuilding.

I agree, but in the meanwhile the expert users could benefit from this.

@23Skidoo
Copy link
Member

Filed #1121 so that we don't forget about minimal rebuilds.

@23Skidoo
Copy link
Member

Fixed in 5417ddd.

@23Skidoo
Copy link
Member

I think that it should be also possible to disable this behaviour. For example, when working on Cabal, I only run cabal-dev install Cabal/ cabal-install/ when I have changed something in the Cabal lib; usually cabal-dev install cabal-install/ is sufficient.

Filed #1143 for this issue.

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