-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
haskellPackages.selda-sqlite: unbreak #405820
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a weak preference for
substituteInPlace --replace-failsince that would let us know when to remove this.FTR, we intentionally leave conditionals alone NixOS/jailbreak-cabal@99eac40.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I'm buying the argument made in that commit. The constraints under the flag are required to pick the correct version for a solver - and then to add another peer dependency at the same time for this case.
But none of that applies to us in nixpkgs. The versions we provide are set. The flag configuration is as well. When you hit a constraint and want to jailbreak it, it doesn't matter for us whether it's behind a flag or not.
What am I missing?
Edit: Maybe I am missing some kind of reverse mechanism that sets the flags based on the provided dependencies? I guess I just don't know about this feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A flag conditional may, besides restricting the version ranges, set any number of things including e.g. compilation flags. If the flag is marked as automatic, Cabal will attempt to automatically set it based on the preinstalled (by us) versions of packages. If we remove those constraints, it just has to go with the default value of the flag, which may mean incorrect settings and the build failing incorrectly, e.g. because a CPP var isn't set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not possible with substituteInPlace: this code applies to 3 packages and the whitespace is different in each .cabal file, so you need a regex. However we can make sed fail too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, I guess 3x replace-fail would be easiest to maintain for us (?)