Skip to content

Conversation

@jkoppel
Copy link

@jkoppel jkoppel commented Nov 22, 2024

No description provided.

@ocramz
Copy link
Contributor

ocramz commented May 6, 2025

Hi @bjpop could you please run CI ? Thank you

Copy link
Contributor

@andreasabel andreasabel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a lot of mode changes 755 -> 644 included in this PR, what does this have to do with the motto "Getting cabal build working with modern GHC"?

extra-deps: []

system-ghc: false
install-ghc: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why hardwire these settings here?
E.g. I always work with the opposite settings.

language-python-test


with-compiler: ghc-9.8.4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why hardwire the compiler version here?

@@ -1,5 +1,5 @@
name: language-python-test
version: 0.6.0
version: 0.6.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this PR contain a version bump?
The released version is 0.5.8

utf8-string >= 1 && < 2
build-tools: happy, alex
build-tools: happy >= 1.20, alex
build-tool-depends: happy:happy
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One should not have both build-tools (the old, deprecated way) and build-tool-depends.

@jkoppel
Copy link
Author

jkoppel commented May 9, 2025

My apologies. A few of these changes were accidentally included, including a fews used to help Cubix build but not strictly necessary.

It is very good to learn about build-tool-depends. I've had issues including happy and alex in other projects, and now I should be able to fix them.

Due to very heavy work pressure, and not needing this merged upstream since we depend on our fork, and knowing that no-one else can use the library until this or similar is merged, I unfortunately must decline to take on the work of correcting the PR. I leave that to the rest of the user base.

@bjpop
Copy link
Owner

bjpop commented Jun 6, 2025

Sorry for the delay in looking into this.

Shall I close this PR?

@andreasabel
Copy link
Contributor

Shall I close this PR?

I'd suggest so.

Please consider PR #82 instead.

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.

5 participants