-
Notifications
You must be signed in to change notification settings - Fork 841
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
Q: Does Stack need autogenerated Autoconf artifacts checked into Git? #1543
Comments
@AshleyYakeley I had to remove these in order to be able to update to time-1.6 in GHC as it otherwise breaks GHC's buildsystem GHC's buildsystem needs to regenerate those files and cause subtle but annoying issues for users if files tracked by Git are modified everytime GHC is built.
Works fine:
|
Ah, based on https://stackoverflow.com/questions/47012909/building-the-latest-version-of-process-as-a-dependency , it would probably be good to include the script. What is cabal-install doing differently here, is calling configure the responsibility of cabal-install instead of being part of Cabal-the-library? |
Closing in favor of tracking it by #3534 |
I don't see any behavior from cabal to generate the
I've just sent a PR that will add support for this to Stack #3598:
|
As I don't use Stack myself, I have to relay this question here (hope the issue tracker is a good place):
@AshleyYakeley and me aren't sure about whether Stack requires those files for build-type-configure packages to be in Git, see also
haskell/time@409d7a0#commitcomment-15084597
However, if Stack requires to violate VCS/Autoconf conventions, then I'd consider this a bug in Stack ;-)
The text was updated successfully, but these errors were encountered: