This project is mirrored from Pull mirroring updated .
  1. 22 Sep, 2016 1 commit
    • Herbert Valerio Riedel's avatar
      Update default-language & avoid default-extensions (#3880) · f87738df
      Herbert Valerio Riedel authored
      This upgrades the `default-language: Haskell98` to `Haskell2010`
      and removes `default-extensions: RankNTypes, FlexibleContexts`
      in favor of adding `LANGUAGE` pragmas where needed.
      Moroever, this also drops `LANGUAGE` pragmas which have become redundant
      due to `Haskell2010` (specifically, `EmptyDataDecls`,
      `ForeignFunctionInterface` and `PatternGuards`)
      Finally, an `other-extensions` specification is put in place for the
      `Cabal` library component.
      This helps loading up files directly in GHCi, such as e.g. `ghci Setup.hs`
      without having to specify `-X...` flags.
  2. 06 Sep, 2016 1 commit
  3. 26 Jul, 2016 1 commit
  4. 30 Jan, 2016 1 commit
  5. 25 Jan, 2016 1 commit
  6. 08 Jan, 2016 1 commit
    • Edward Z. Yang's avatar
      Remove same-package import lists, fixes #2835. · 639cd007
      Edward Z. Yang authored
      Instead of qualifying, in some cases I just added an extra
      'hiding' pragma to squelch errors.  Common conflicts
      (just grep for hiding):
          - Flag
              - Distribution.Simple.Compiler
              - Distribution.PackageDescription
              - Distribution.Simple.Setup
          - installedComponentId
              - Distribution.Package
              - Distribution.InstalledPackageInfo
          - doesFileExist
              - Distribution.PackageDescription.Check
          - instantiatedWith
              - I renamed the field in InstalledPackageInfo.  But
                it's probably going away with Backpack bits; I
                migth just excise it soon.
          - absoluteInstallDirs and substPathTemplate
              - Distribution.Simple.InstallDirs
              - Distribution.Simple.LocalBuildInfo
      I fixed some shadowing errors by renaming local variables in some cases.
      Common shadowings (we should perhaps consider not using these as
      method/field names):
          - freeVars
          - components
          - noVersion
          - verbosity
          - get
          - description
          - name
      Some data structures were moved around (IPIConvert and ABIHash)
      to make it easier to handle import lists.
      Some functions in Utils could be turned into reexports of standard
      library functions.
      No explicit imports were removed from non-Cabal imports.  These
      imports help maintain warning cleanliness across versions of GHC,
      so I don't recommend removing them.
      Signed-off-by: default avatarEdward Z. Yang <>
  7. 07 Dec, 2014 1 commit
    • Lennart Spitzner's avatar
      Change globalCommands description generation · d54a98b1
      Lennart Spitzner authored
      - previously, runCommands internally modified the description
        by adding the list of commands.
      - now, globalCommands is a function that builds the complete
        description without need for changes during runCommands invocation.
      - slightly more code duplication, but better separation of concerns
  8. 14 Apr, 2014 1 commit
  9. 02 Feb, 2014 1 commit
  10. 03 Nov, 2012 1 commit
  11. 23 Oct, 2011 1 commit
  12. 19 Jun, 2011 1 commit
  13. 18 Dec, 2010 1 commit
  14. 27 Jul, 2010 1 commit
  15. 28 Dec, 2009 1 commit
  16. 28 Jun, 2008 1 commit
    • Duncan Coutts's avatar
      Update module headers · 0c993c84
      Duncan Coutts authored
      Use as the maintainer in most cases except for
      a few which were pre-existing modules copied from elsewhere or modules
      like L.H.Extension which really belong to
      Remove the useless stability module. We have more detailed information
      on stability elsewhere (in the version number and user guide).
      Add more top level module documentation, taken from the source guide.
  17. 26 Jun, 2008 1 commit
  18. 27 Mar, 2008 1 commit
    • Duncan Coutts's avatar
      Rename various *Verbose fields to *Verbosity instead · 556b9877
      Duncan Coutts authored
      Despite appearances this is actually not completely pointless.
      For the Cabal-1.4 branch we need the *Verbose fields to have the
      same types as they did in Cabal-1.2, becuase lots of Setup.hs
      scripts use them and our change to make them all have type Flag
      makes many Setup.hs scripts fail. A solution for the 1.4 branch
      is to rename the real field and to add the old field back in.
      To keep as much similarity as possible between the HEAD and 1.4
      branches I'm applying the name change in both.
      On the plus side it's a better name anyway.
  19. 26 Mar, 2008 1 commit
  20. 21 Mar, 2008 1 commit
  21. 16 Feb, 2008 1 commit
  22. 05 Feb, 2008 1 commit
  23. 27 Jan, 2008 1 commit
  24. 21 Jan, 2008 1 commit
  25. 17 Dec, 2007 1 commit
  26. 15 Dec, 2007 1 commit
    • Duncan Coutts's avatar
      Make all command line flags and flag collection types monoids · 1352ee0b
      Duncan Coutts authored
      And specify command flags in a way that allows converting from or two strings.
      So not only can we parse command lines into the various flag types, we can
      convert back. This is crucial in cabal-install so that we can call Setup.hs
      scripts with all the various args, and override certain flags in a typed way
      rather than just representing them all as strings.
  27. 20 Nov, 2007 1 commit
  28. 03 Sep, 2007 1 commit
  29. 26 Aug, 2007 1 commit
  30. 14 Aug, 2007 1 commit
  31. 31 Jul, 2007 1 commit
  32. 23 Jun, 2007 1 commit
  33. 24 Jul, 2007 1 commit
  34. 04 Jun, 2007 1 commit
  35. 14 May, 2007 2 commits
    • Ian Lynagh's avatar
      Fix a warning · 79783876
      Ian Lynagh authored
    • Ian Lynagh's avatar
      Make a proper verbosity type, rather than using Int values · 28847431
      Ian Lynagh authored
      Hopefully this will make it easier to get better verbosity consistency.
      We could, by changing only Distribution.Verbosity, use
      "type Verbosity = Int" for now to give users of the library a chance to
      catch up, but the upcoming Cabal release seems like a good opportunity
      to cram in as much of the interface-changing stuff that we want to do
      as we can. I think the added benefit of a slow switch would be very low
  36. 09 Mar, 2007 1 commit
    • Simon Marlow's avatar
      Add 'setup makefile' command · 66328e57
      Simon Marlow authored
      'setup makefile' generates a Makefile that performs the steps
      necessary to compile the Haskell sources to object code.  This only
      works for libraries, and only with GHC right now.
      Instead of simply 'setup build', you can do this:
        $ ./setup makefile
        $ make
        $ ./setup build
      where './setup makefile' does the preprocessing and generates a
      Makefile tailored to the current package.  'make' will build all the
      Haskell code to object files, and 'setup build' will build any C code
      and the library archives.
      The reason for all this is that you can say 'make -j' and get a
      parallel build, or you can say
        make dist/build/Foo.o EXTRA_HC_OPTS=-keep-s-file
      to compile a single file with extra options.
  37. 22 Mar, 2007 1 commit
  38. 13 Jan, 2007 1 commit
  39. 11 Jan, 2007 1 commit