Skip to content
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

per-package configuration #900

Closed
bos opened this issue May 24, 2012 · 2 comments
Closed

per-package configuration #900

bos opened this issue May 24, 2012 · 2 comments

Comments

@bos
Copy link
Contributor

bos commented May 24, 2012

(Imported from Trac #910, reported by @kowey on 2012-01-02)

This may be related to #223 but I don't particularly want it in my global config. I'm sick of running "cabal build" and not noticing until much later that my test had a compile error because I'd neglected to reconfigure with "--enable-test".

A similar issue happens with packages with custom flags, say sometimes I lose the "-f-library" flag I sometimes use for faster compilation.

I wish I had a mechanism to remember the command line flags passed in for a particular package. Editing my global config doesn't seem quite like what I'm looking for; it has to be something that works, eg. with different branches of the same package. What might be better for me is something like the Darcs prefs system, where I could edit a file in the current working directory like ".cabal" that says something like

configure --enable-test -f-library
install -fgui
@bos
Copy link
Contributor Author

bos commented May 24, 2012

(Imported comment by @kosmikus on 2012-01-02)

Also see #780 and #556.

@gbaz
Copy link
Collaborator

gbaz commented Aug 28, 2021

i believe this is obsoleted by the project stuff with new-configure.

@gbaz gbaz closed this as completed Aug 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants