GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
(Imported from Trac #446, reported by awick on 2009-01-07)
The config file for cabal-install lets me set all sorts of useful paths, except for the non-compiler tools. In other words, there's no config file mapping for the --with-PROG or --PROG-options flags, which would be really convenient.
(At least, when I tried the obvious versions, it didn't work. Maybe missing docs somewhere?)
(Imported comment by awick on 2009-01-07)
The (now) attached patch set implements the behavior we were looking for, but probably does it in the wrong way. Specifically, I couldn't figure out an easy way to use ProgramConfiguration? to carry the information around such that the right flags could be added during load and spit out during use. So I added another data structure and used that.
Hopefully either not using ProgramConfiguration? was the right thing to do, or these patches will help in doing it the right way.
The patches apply cleanly to cabal-install 0.6.0.
(Imported comment by awick on 2009-02-01)
updated version of the patches
(Imported comment by @dcoutts on 2009-02-10)
Sigh, I wish trac let one search for tickets with patches so things like this would not get lost. :-(
(Imported comment by @dcoutts on 2011-01-11)
This would be particularly useful for negating the new ghc default that -rtsopts is needed to do any profiling or tracing.
Seems long-obsolete. Close?
As best as I can parse, this is asking for what we have now in the program-locations and the program-default-options stanzas of the cabal config file. I'm closing. If I missed something, please comment and reopen.