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

Nix integration improvements #4193

Merged
merged 5 commits into from Jan 2, 2017
Merged

Nix integration improvements #4193

merged 5 commits into from Jan 2, 2017

Conversation

ttuegel
Copy link
Member

@ttuegel ttuegel commented Dec 30, 2016

The Nix expressions for Cabal and cabal-install are updated. Nix expressions are instantiated in a "fake" Nix shell to cope with environment impurities introduced by newer versions of cabal2nix. cabal looks at the CABAL_IN_NIX_SHELL environment variable instead of IN_NIX_SHELL; it was pointed out that cabal need not care if it is running inside nix-shell because we only care if we are running in a shell created by cabal.

@laura-dietz
Copy link

Does this not require some changes in documentation?

@ttuegel
Copy link
Member Author

ttuegel commented Dec 30, 2016

It does, but I need it to build first! 😃 For some reason Travis won't run on my personal branch anymore...

cabal2nix recently changed its generated expressions to read the
IN_NIX_SHELL environment variable. Now we need to set this variable when
calling nix-instantiate to produce the same result as calling nix-shell.
cabal only cares if it is running in a Nix shell that was started by
another cabal process, so we should not read IN_NIX_SHELL; rather, we
read a cabal-specific variable for that purpose.
Mention that we allow `shell.nix` or `default.nix`, the same as
`nix-shell`.
@grayjay
Copy link
Collaborator

grayjay commented Jan 3, 2017

For some reason Travis won't run on my personal branch anymore...

I think it is the branch whitelist:

cabal/.travis.yml

Lines 7 to 15 in 19d9738

# Remember to add release branches
# we whitelist branches, as we don't really need to build dev-branches.
branches:
only:
- master
- "1.24"
- "1.22"
- "1.20"
- "1.18"

@23Skidoo
Copy link
Member

23Skidoo commented Jan 3, 2017

Branches with corresponding PRs shouldn't be affected by the whitelist...

@ttuegel
Copy link
Member Author

ttuegel commented Jan 3, 2017

Travis does run on the PR, it just doesn't run on my personal clone anymore (unless I open a PR). That's why I opened this PR before it was really ready. It would be nice if the Travis web interface would indicate that the whitelist is blocking a branch... The branch still appeared in the web interface, so I was very confused why Travis would not build it.

@ysangkok ysangkok mentioned this pull request Feb 17, 2017
3 tasks
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.

None yet

4 participants