This project is mirrored from Pull mirroring updated .
  1. 03 May, 2007 6 commits
  2. 22 Apr, 2007 2 commits
  3. 10 Apr, 2007 1 commit
  4. 09 Apr, 2007 2 commits
  5. 19 Jun, 2011 1 commit
  6. 18 Jun, 2011 2 commits
  7. 17 Jun, 2011 1 commit
  8. 25 May, 2011 2 commits
  9. 24 May, 2011 4 commits
  10. 18 May, 2011 1 commit
    • Duncan Coutts's avatar
      Do a sanity check on the HookedBuildInfo · 91a6d9fb
      Duncan Coutts authored
      Fixes ticket #844. Previously the function that merged the HookedBuildInfo
      into the PackageDescription would add a library section even if none
      previously existed.
      Now we generate an error message if the HookedBuildInfo contains info
      for non-existant components (libs/exes), e.g:
      Setup: The buildinfo contains info for a library, but the package does not
      have a library.
  11. 17 May, 2011 1 commit
  12. 16 May, 2011 1 commit
  13. 17 May, 2011 1 commit
    • Duncan Coutts's avatar
      Reimplement createDirectoryIfMissingVerbose to use sensible file permissions · 237cfe10
      Duncan Coutts authored
      Hopefully should fix ghc ticket #4982.
      The problem was permissions on directories: previously we used ordinary
      createDirectory and on unix this creates dirs using the current user's
      umask. If the root user has a silly umask then someone doing sudo
      install will end up with dirs that are not readable by non-root users.
      So the solution is to do the same as we do with files: override the
      umask and explicitly set the file permissions based on the kind of
      file: ordinary file, executable file and now also directory.
      Sadly we also had to re-implement createDirectoryIfMissing to use our
      new createDirectory wrapper function.
  14. 08 May, 2011 1 commit
  15. 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.
  16. 06 Oct, 2009 1 commit
  17. 15 Apr, 2011 1 commit
    • Duncan Coutts's avatar
      Implement Setup sdist --output-directory=dir · e41906a7
      Duncan Coutts authored
      That is, allow generating a dir tree rather than a tarball.
      Apart from being useful directly, this is the right approach for
      tools like cabal-install. cabal-install does the tar step itself
      and might like to do other things like zip format.
      Also cleaned up the sdist code a little.
  18. 27 Apr, 2011 1 commit
  19. 26 Apr, 2011 2 commits
  20. 28 Mar, 2011 1 commit
  21. 30 Mar, 2011 2 commits
  22. 11 Apr, 2011 1 commit
  23. 01 Apr, 2011 1 commit
    • ttuegel's avatar
      Fix for test suite stanzas with conditionals. · 3922bde0
      ttuegel authored
      Ticket #811. This fixes a problem where Cabal would fail to detect the "type"
      field of a test suite when the test suite contained a conditional. Conditionals
      can now be used, with the restriction that the "type" field and the appropriate
      "main-is" or "test-module" field must be specified together in any conditional
      branch where they occur.
  24. 03 Mar, 2011 1 commit
  25. 19 Jan, 2011 1 commit
  26. 17 Apr, 2011 1 commit
    • Ian Lynagh's avatar
      Refactor to avoid problems when $HOME is not set · cbe50672
      Ian Lynagh authored
      We now avoid calling getWindowsProgramFilesDir and
      getAppUserDataDirectory when we don't need to know their results.
      This means that a GHC build goes through when $HOME is unset
      (GHC trac #5047).