This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 20 May, 2007 4 commits
  2. 08 May, 2007 1 commit
  3. 06 May, 2007 1 commit
  4. 04 May, 2007 2 commits
  5. 03 May, 2007 11 commits
  6. 22 Apr, 2007 2 commits
  7. 10 Apr, 2007 1 commit
  8. 09 Apr, 2007 2 commits
  9. 19 Jun, 2011 1 commit
  10. 18 Jun, 2011 2 commits
  11. 17 Jun, 2011 1 commit
  12. 25 May, 2011 2 commits
  13. 24 May, 2011 4 commits
  14. 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.
      91a6d9fb
  15. 17 May, 2011 1 commit
  16. 16 May, 2011 1 commit
  17. 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.
      237cfe10
  18. 08 May, 2011 1 commit
  19. 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
      accordingly.
        
      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.
      2e348126