This project is mirrored from Pull mirroring updated .
  1. 11 Aug, 2012 1 commit
  2. 19 Jun, 2012 1 commit
  3. 19 May, 2012 1 commit
  4. 29 Mar, 2012 1 commit
    • Duncan Coutts's avatar
      Extend the --package-db= feature to allow multiple dbs and start from empty · dfb50c35
      Duncan Coutts authored
      Previously only one --package-db flag was used (later ones overrode earlier).
      Internally we can handle stacks of package dbs, now we expose that fully in
      the user interface.
       --global sets the initial db stack to [GlobalPackageDB]
       --user sets the initial db stack to [GlobalPackageDB, UserPackageDB]
       --package-db=clear clears the db stack to []
       --package-db=global pushes GlobalPackageDB on the top of the stack
       --package-db=user pushes UserPackageDB on the top of the stack
       --package-db=${file} pushes SpecificPackageDB ${file} on the top of the stack
      So --global and --user just affect the initial db stack, and this can be
      extended by the --package-db flag, or reset using --package-db=clear.
      Note that although this lets users tell cabal to avoid using the global
      package db, we cannot yet stop ghc from looking at the global package db.
      Fixes feature request #437.
  5. 23 Oct, 2011 1 commit
  6. 11 Oct, 2011 1 commit
  7. 25 Aug, 2011 1 commit
  8. 08 Aug, 2011 1 commit
  9. 08 Jul, 2011 1 commit
    • Duncan Coutts's avatar
      Fix withComponentsLBI and move Components to LocalBuildInfo module · 1c20a632
      Duncan Coutts authored
      An annoyance of the current Simple build system is that each phase
      (build, install, etc) can be passed additional HookedBuildInfo which
      gets merged into the PackageDescription. This means that we cannot
      process the PackageDescription up front at configure time and just
      store and reuse it later, we have to work from it each time afresh.
      The recent addition of Components (libs, exes, test suites) and a
      topoligical sort of the components in the LocalBuildInfo fell foul
      of this annoyance. The LocalBuildInfo stored the entire component
      which meant they were not updated with the HookedBuildInfo. This
      broke packages with custom Setup.hs scripts that took advantage of
      the HookedBuildInfo feature, including those with configure scripts.
      The solution is to store not the list of whole components but the
      list of component names. Then withComponentsLBI retrieves the actual
      components from the PackageDescription which thus includes the
      Also moved the Components into an internal module because (for the
      moment at least) it is part of the Simple build system, not part of
      the package description.
  10. 19 Jun, 2011 1 commit
  11. 08 May, 2011 1 commit
  12. 05 May, 2011 1 commit
    • intractable's avatar
      intrapackage-deps-and-per-component-preprocessing · 2e348126
      intractable authored
      This patch adds intrapackage dependency resolution so that components
      (libraries, exes, test suites) are build in the correct order.  This mean it's
      now possible to have, e.g., executables that depend on other executables defined
      in the same package description: the build-tools namespace has been extended
      Related to this change is the refactoring of the do-it-all preprocessSources
      function, formerly invoked by initialBuildSteps, into a a function
      preprocessComponent that is invoked when a component is being built.  This lets
      us use executables defined in a package to be used as a custom preprocessor when
      building other components.
      Finally, a number of functions now operate on values of the sum type
      PackageDescription.Component rather than specifically operating on Library or
      Executable and so forth.
  13. 06 Oct, 2009 1 commit
  14. 30 Jan, 2011 2 commits
  15. 29 Jan, 2011 1 commit
    • Duncan Coutts's avatar
      Get the mapTreeData util from the right place · 97f266be
      Duncan Coutts authored
      Originally Thomas had moved them to Distribution.PackageDescription
      but I'm rather of the opinion that the functions (and the data
      structure) that they manipluate is ugly and I'd rather keep them
      hidden away in a less public module.
  16. 10 Jan, 2011 1 commit
    • ttuegel's avatar
      Tracking enabled/disabled TestSuites in PackageDescription. · f0a2d5e3
      ttuegel authored
      This patch adds the 'testEnabled' field to TestSuite. It's 
      undesirable to track build status information in the static package 
      description, but there is no better solution at this time. This 
      patch has the side-effect of fixing several TODOs in 
  17. 18 Oct, 2010 2 commits
  18. 16 Oct, 2010 1 commit
  19. 13 Oct, 2010 2 commits
    • Duncan Coutts's avatar
    • Duncan Coutts's avatar
      Change the syntax and behaviour of the cabal-version field · 520b3481
      Duncan Coutts authored
      For historical reasons the cabal-version is specified with a version range,
      to indicate the range of versions of tools that the package will work with.
      We now think it makes more sense to specify the version of the Cabal spec
      that the package follows. Old Cabal versions will not be able to parse simple
      versions in this field. So we initially make the parser allow plain versions
      but then we add a check to warn about using it prior to Cabal-1.12 at which
      point it will be allowed.
      Added a check about using version ranges that are not of the form '>= x.y'.
      Also change behaviour to ignore upper bounds in the given version range.
  20. 10 Oct, 2010 2 commits
  21. 25 Aug, 2010 1 commit
    • adept's avatar
      Auto-reconfiguration when .cabal is newer than setup-config · 549a6985
      adept authored
      This patch adds "ConfigFlags" to the "LocalBuildInfo" and reuses them to
      perform "configureAction" when .cabal file is changed. This has
      the same effect as re-running "configure" with the most recent used
      set of options, which should be the sensible thing to do.
      Closes #294, #477, #309 and #518.
  22. 07 Jun, 2010 1 commit
  23. 26 May, 2010 2 commits
    • ttuegel's avatar
      Conditional inclusion of testsuites · 10aa1d31
      ttuegel authored
      Ticket #215 (Overhaul support for packages' tests). The
      "--enable-tests" and "--disable-tests" command-line flags are
      introduced, with "--disable-tests" being the default. If tests
      are disabled, the testsuites are stripped from the
      GenericPackageDescription during the configure stage, before
      dependencies are resolved.
    • ttuegel's avatar
      Configure and build executable testsuites · d16062cc
      ttuegel authored
      Ticket #215 (Overhaul support for packages' test). During the
      build stage, executable testsuites are handled analogously to
      ordinary executables. This means their sources are
      preprocessed and compiled. To actually compile, the build
      stage actions are performed on a dummy Executable.
  24. 22 Apr, 2010 1 commit
  25. 30 Mar, 2010 1 commit
  26. 15 Dec, 2009 1 commit
  27. 15 Apr, 2010 1 commit
    • Duncan Coutts's avatar
      Also check compiling C headers at configure-time · 802596ac
      Duncan Coutts authored
      So we now both check if the headers can be pre-processed and separately
      if they can be compiled. If it fails the pre-processing check then it
      is usually (but not always) a missing header. If it fails to compile
      then it is definately borked, not missing. Error messages reflect this.
  28. 09 Apr, 2010 1 commit
    • kmcallister's avatar
      better error messages for erroneous local C headers · 393e4213
      kmcallister authored
      Addresses the issue in tickets #532, #648.
      When the all-together test of C libraries and headers fails, use only the
      preprocessor to probe the headers individually.  If they all check out,
      give a more equivocal error message and suggest -v3.
  29. 20 Mar, 2010 1 commit
    • Duncan Coutts's avatar
      Fix local inplace registration for ghc-6.12 · 2ff64d8a
      Duncan Coutts authored
      This is for the case of intra-package deps where the lib has to be
      registered into a local package db. We use "-inplace" suffix for
      the local installed package ids (rather than using an ABI hash).
  30. 23 Dec, 2009 2 commits
    • Duncan Coutts's avatar
      Simplify getInstalledPackages and callers · 6082b0fc
      Duncan Coutts authored
      No longer returns Maybe, we can find installed packages for all
      the compilers we support (and this feature is a requirement for
      support for new compilers).
      This is an API change so cannot merge to Cabal-1.8.x branch.
    • Duncan Coutts's avatar
      Implement support for hugs and nhc98 package databases · 42cf79ce
      Duncan Coutts authored
      That is, work out which packages are installed for hugs and nhc98.
      In both cases there is special support for the core packages.
      In future both should use the standard method when they supply
      proper installed package info files for the bundled libraries.
  31. 16 Dec, 2009 1 commit
  32. 20 Nov, 2009 1 commit
  33. 06 Oct, 2009 1 commit
  34. 05 Oct, 2009 1 commit