Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
Cabal
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Contributor analytics
CI/CD analytics
Repository analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Haskell
Cabal
Commits
1917116f
Commit
1917116f
authored
19 years ago
by
Isaac Potoczny-Jones
Browse files
Options
Downloads
Patches
Plain Diff
updated todos
parent
12a1602e
No related branches found
Branches containing commit
Tags
2009-06-25
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
TODO
+1
-20
1 addition, 20 deletions
TODO
with
1 addition
and
20 deletions
TODO
+
1
−
20
View file @
1917116f
...
...
@@ -5,27 +5,8 @@
into a subdirectory, so we can build the Setup file with the normal
invocation of cabal.
* Clean up readme according to Simon's suggestions
- to install globally / with root access: should "just work"
- to install just for me: copy+hide Cabal-1.0, then install the
new one with --user.
* grab and test:
> Another option is to patch the PreProcess.hs module to check to see if
> cpphs exists and if not, to use "raw" cpp, or cpp through ghc or
> something. If someone does this, they should also patch the sanity
> checker to add a warning.
I've fixed this now (as per your last paragraph above), and done some
rudimentary testing. I didn't add a warning though; perhaps we should,
but since it's using the same preprocessor that will be used when
compiling with GHC anyway, I'm not sure a warning will be terribly
helpful.
I hope this can sneak into the Cabal release, but don't worry if not.
* add a haskell-version field?
* ignore unknown fields? (--force?)
-= 1.0 =-
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment