This project is mirrored from Pull mirroring updated .
  1. 01 May, 2008 7 commits
  2. 30 Apr, 2008 1 commit
  3. 29 Apr, 2008 2 commits
    • Duncan Coutts's avatar
      Change handling of bool command line args to allow an unset state · fb993c2a
      Duncan Coutts authored
      For bool valued flags we were always producing the command line
      string corresponding to a false flag value, even if the flag was
      not set. For example we'd always get "--disable-shared".
      It is important for cabal-install to be able to take an empty set
      of flags, override a few flags and turn the flags back into
      command line strings without getting a lot of extra defaults.
      Partly this is because we have to work with older versions of the
      Cabal library command line which does not recognise the new options.
    • Duncan Coutts's avatar
      Remove the feature for highlighting the default cases in --help output · d49d15a7
      Duncan Coutts authored
      Turns out it doesn't help us much because in many cases the initial/default
      flags are actually empty so we cannot identify the default values.
  4. 28 Apr, 2008 2 commits
  5. 26 Apr, 2008 1 commit
    •'s avatar
      Fix fix for #224. · 7e69b6f4 authored
      Changing from list of Dependencies to Maps resulted in the wrong Monoid 
      instance being used.  I'd still like to be able to run a test suite on 
      this but that'd require a lot more work to do properly...
  6. 23 Apr, 2008 5 commits
    • Duncan Coutts's avatar
      When multiple specifying list fields in the same section combine them · 48c8903b
      Duncan Coutts authored
      eg if you had:
      extensions: Foo
      extensions: Bar, Baz
      then previously we only ended up with [Bar, Baz]. Now we get them all.
      Only applies to list fields, for single fields the second value is taken
      and the first is silently discarded. This isn't good of course but the
      fix is harder since we're not in a context where we can report errors.
      Really we should just declare up front what kind of field it is and
      inherit the right behaviour automagically, either duplicates disallowed
      or allowed and combined with mappend.
    • Duncan Coutts's avatar
      Normalise file names in warning messages · 9d3299ad
      Duncan Coutts authored
      We already do this for error messages.
    • Duncan Coutts's avatar
      Fix the check for -XFooBar ghc-options flags to be more permissive · eb148937
      Duncan Coutts authored
      Previously we rejected all such flags but that posed the problem that older
      versions of Cabal, like 1.1.6 did not understand new extensions so we
      could not actually follow the advice and use the extenion. So now we only
      warn about -X flags if they refer to old extensions that Cabal 1.1.6 knew
      about. If the .cabal file specifies cabal-version: >= 1.2 or similar
      (anything that excludes 1.1.6) then we warn about all -X flags.
    • Duncan Coutts's avatar
      Add checks for unknown OS Arch and Compiler names · 99ec2dca
      Duncan Coutts authored
      They're ok locally but for distribution they need to be known.
    • Duncan Coutts's avatar
      Package check now take a GenericPackageDescription · 87ec8824
      Duncan Coutts authored
      Unfortunately in some cases we only have a already-configured
      PackageDescription to we have to expose a checkConfiguredPackage.
      We should refactor things so that we keep all the information
      even in a configured PackageDescription.
  7. 22 Apr, 2008 3 commits
  8. 20 Apr, 2008 2 commits
    • Duncan Coutts's avatar
      Don't nub extra-libs in unionBuildInfo · d9233d60
      Duncan Coutts authored
      It's possible that we sometimes need to list the same library
      more than once if there are circular symbol references.
    • Duncan Coutts's avatar
      Fix unionBuildInfo · fd3d86e1
      Duncan Coutts authored
      Fix ticket #264 to use nub only on the fields which are treated as sets.
      Probably we should be using the right types and mappend for each field.
      Change to construct a new value from scratch rather than overriding one
      of the two args. This helps to make sure we're updating all the field
      as we get a warning if we miss any. Turns out we were missing the ghc
      profiling and shared libs options which meant they were getting dropped.
      That had the effect of ghc-prof-options: in .cabal files being ignored.
      Thanks to 'midfield' from #haskell for spotting this.
  9. 15 Apr, 2008 2 commits
  10. 13 Apr, 2008 6 commits
  11. 17 Apr, 2008 2 commits
  12. 12 Apr, 2008 1 commit
  13. 09 Apr, 2008 4 commits
    • Duncan Coutts's avatar
      Check for the required cabal version early in parsing · b6137f68
      Duncan Coutts authored
      Previously we only checked the "cabal-version" field after parsing
      and all other configure processing. If the package really needs a
      later Cabal version it is of course highly likely that parsing or
      configure are going to fail and the user is not going to get the
      helpful error message about the version of Cabal required. So now
      we do the check early during parsing. If a later version is
      required and parsing subsequently fails, we now report the version
      issue, not the subsequent parse error. If parsing succeeds we
      still issue a warning which should be a useful hint to the user if
      subsequent configure processing fails.
    • Duncan Coutts's avatar
      Use relative file paths in .cabal parse error messages · 8d931884
      Duncan Coutts authored
      Do this by normalising the file path in the error message
      and when looking for .cabal files, by looking in '.' rather
      than the absolute path of the current directory.
    • Duncan Coutts's avatar
      Remove unused import · 2fea05a5
      Duncan Coutts authored
    • Duncan Coutts's avatar
      Fix for detecting ~/.cabal/ dir as a .cabal file · ecf19959
      Duncan Coutts authored
      Which happened if you use cabal configure in your home dir.
      Now produced the right error message, or if you actually put
      a cabal project in your home dir, it might actually work.
      Also, do the same fix for findHookedPackageDesc.
  14. 08 Apr, 2008 1 commit
  15. 07 Apr, 2008 1 commit
    • Duncan Coutts's avatar
      Fix names of profiling libs · bd530c9f
      Duncan Coutts authored
      I broke this recently when refactoring. Restore the original behaviour.
      Was generating "libHSfoo_p-1.0.a" when it should be "libHSfoo-1.0_p.a".