-
Notifications
You must be signed in to change notification settings - Fork 339
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
Prune Setup.hs
#7127
Comments
The (only) job of Why should We could skip this step and provide a script instead that does the job, and instruct packagers and admins to use the script. |
Some alternatives for generating the Generate
|
This kind of ad-hoc overriding of safety checks seems dangerous. |
That's definitely a no. The repo is already too fat (my |
I'm not seeing the benefits here. All the suggested alternatives for generating the agdai files put either more work on the developers or on the package maintainers. Your main complaint with Setup.hs seems to be lack of documentation, which I think is best addressed by adding documentation. If someone wants to cross-compile Agda, they can use the workaround suggested in the issue until it's been fixed. |
Does Agda really need a
Setup.hs
file?Reasons to migrate away from
Setup.hs
:Setup.hs
Setup.hs
prevents cross-compilationSetup.hs
is needed at allSetup.hs
vs e.g. the.cabal
fileMakefile
, regarding the-quicker
suffixIOTCM
APIs, which it calls.agdai
)build-type: Simple
(and noSetup.hs
file)data/
)pandoc -D latex
etc.)The text was updated successfully, but these errors were encountered: