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

setupAndCabalTest uses cabal act-as-setup for cabal part #6643

Merged
merged 2 commits into from
Apr 3, 2020

Conversation

phadej
Copy link
Collaborator

@phadej phadej commented Apr 2, 2020

No description provided.

@phadej phadej changed the title Cabal testsuite src dir setupAndCabalTest uses cabal act-as-setup for cabal part Apr 2, 2020
@phadej
Copy link
Collaborator Author

phadej commented Apr 2, 2020

I opened this PR with improper name first. It should been "setupAndCabalTest uses cabal act-as-setup for cabal part" .

The cabal command interface will drift more and more from
./Setup interface. This is first step: don't assume
they are the same.

This removes need to "patch" setup commands to work with cabal:
the `act-as-setup` SHOULD behave as (simple) ./Setup

There were few setupAndCabalTests which weren't `build-type: Simple`.
For those I made a separate `cabal.test.hs`.

Also added a OutputNormalizer for global tmp directory.
`v2-build` sdists `build-type: Custom` packages to get the list of files
to watch. I guess it's ok to have that functionality,
yet it could be eventually removed, as `v2-sdist`
does not invoke `./Setup.hs` script.
@phadej phadej force-pushed the cabal-testsuite-src-dir branch from 7196b28 to ab35536 Compare April 3, 2020 10:52
@phadej phadej merged commit 1008805 into haskell:master Apr 3, 2020
@phadej phadej deleted the cabal-testsuite-src-dir branch April 3, 2020 13:20
@phadej phadej added this to the 3.4.0.0-rc1 milestone Jul 10, 2020
@phadej phadej mentioned this pull request Jul 10, 2020
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

Successfully merging this pull request may close these issues.

1 participant