On Sat, Mar 26, 2011 at 2:28 PM, Yitzchak Gale <g...@sefer.org> wrote: > Thanks for the fantastic cabal-dev tool!
You're welcome! > Is there any convenient way to save changes to the > package-specific cabal config file in cabal-dev? .... > The only solution I have found so far is to run > cabal-dev install once (ignoring the errors) to create > the cabal-dev directory and cabal.config, make a > copy of cabal.config with a different name, edit it > as needed, and then use a long-winded > "--config=..." option for every subsequent run > cabal-dev. That is currently the only way to do this :(. One workaround is to create an alias for cabal-dev that adds that flag. e.g., in Bash: alias cabal-dev = 'cabal-dev --config=cabal.config ' Then you can have a cabal.config next to your project cabal file and it will use that. To bypass the alias, just prefix it with "\", e.g.: $ \cabal-dev We're working on the first problem -- it's just a matter of finding the time. Unfortunately, that's probably not going to happen for another week or two. The ticket is here: https://github.com/creswick/cabal-dev/issues#issue/15 --Rogan > > The changes I need to make are as follows: > > - remote-repo-cache is wrong for Mac OS X > - add more remote-repo lines for our local > yackage servers. > > Note that the first is global, so it would be nice > to have a way to make that change once globally > for all packages. Whereas the second is, in > general, package specific. > > We find local yackage servers much simpler to use > and far more powerful than using add-source. > You can organize packages by project, team, > specific developers, etc. > > Thanks, > Yitz > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe > _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe