This project is mirrored from Pull mirroring updated .
  1. 27 Dec, 2016 1 commit
    • Edward Z. Yang's avatar
      Refactor Backpack data structures to be less flexible. · 28af355b
      Edward Z. Yang authored
      There were a number of fields in 'LinkedComponent' which
      were "too" flexible, in that they were fully determined by
      other fields in the structure.  This refactor deletes those
      fields and replaces them with functions that refer to the
      fields directly.
      I also introduce a new type, ComponentInclude, to take
      the place of tuples which were used to represent includes
      (mixins) in Backpack.
      There's also more documentation for lots of bits.
      Signed-off-by: default avatarEdward Z. Yang <>
  2. 21 Dec, 2016 1 commit
  3. 18 Dec, 2016 2 commits
  4. 17 Dec, 2016 1 commit
  5. 13 Dec, 2016 7 commits
  6. 09 Dec, 2016 1 commit
  7. 08 Dec, 2016 1 commit
  8. 07 Dec, 2016 3 commits
  9. 05 Dec, 2016 1 commit
  10. 29 Nov, 2016 1 commit
  11. 27 Nov, 2016 2 commits
  12. 26 Nov, 2016 1 commit
    • tulcod's avatar
      Implement foreign library versioning · 8744e30b
      tulcod authored
      This adds support for building foreign libraries with a given ABI version on Linux. This is enables foreign libraries to specify ABI compatibility information. This is important since ABI compatibility differs from package release versions.
      Two new fields are added: lib-version-info and lib-version-linux. The former accept versions Libtool-style, the latter sets SONAME versions directly. In both cases, appropriate symlinks are installed.
      Libtool accepts ABI version data via the -version-info flag, which takes current[:revision[:age]] data. This is then parsed into a version number. We copy this approach so that library versioning may be generalised to other operating systems than Linux.
  13. 18 Nov, 2016 1 commit
  14. 17 Nov, 2016 1 commit
  15. 16 Nov, 2016 1 commit
  16. 15 Nov, 2016 1 commit
  17. 14 Nov, 2016 3 commits
  18. 13 Nov, 2016 1 commit
  19. 12 Nov, 2016 1 commit
    • Duncan Coutts's avatar
      Fix implementation of addBuildableCondition · 40d1b4f1
      Duncan Coutts authored
      The addBuildableCondition function was added to solve the problem with
      "buildable: False". The problem was that we would solve or check
      dependencies on the basis of the component in question being needed, and
      then at the end discover that the component is actually not buildable at
      all, and if we'd known that up front we would not have solved for the
      component's dependencies.
      The trick that addBuildableCondition does is a syntactic transformation,
      from components like:
      executable blah
        buildable: False
        build-depends: foo >= 1, bar < 2
        something-else: whatever
      executable blah
        -- empty!
      Or at least, that's the intention. In the above situation the
      implementation of addBuildableCondition returns an empty CondNode:
      CondNode mempty mempty []
      The type at which mempty is used is important here. This transformation
      is used in two places: one in the solver and the other in finalizePD.
      In the solver the mempty is used at types from the PackageDescription:
      Library, Executable, TestSuite etc. So in this case the transformation
      works fine we end up with empty executables, test suites etc.
      In finalizePD however the mempty gets used at type PDTagged (which is
      sort of a union of Library, Executable etc plus none/null) and the
      mempty for PDTagged is PDNull which means it does not even specify
      which component we're referring to. So effectively that means instead of
      ending up with an empty executable in the above example, we end up
      deleting the executable entirely!
      This was a change in behaviour. Prior to adding addBuildableCondition
      the result of finalizePD would include non-buildable components and the
      rest of the build system infrastructure was set up to skip over them
      when building. The change was not noticed precisely because the rest of
      the system was already set up to ignore non-buildable components.
      This is not however a benign change in behaviour. In particular in
      cabal-install in the install plan we end up completley forgetting about
      all the non-buildable components. This means we cannot even report that
      components are non-buildable when users ask to build them, because we've
      completely forgotten that they exist.
      So this patch keeps the original addBuildableCondition for use by the
      solver since the solver uses it at sensible monoid types. The patch adds
      a special version for the PDTagged type which changes the transformation
      so that in the above example we end up with:
      executable blah
        buildable: False
        something-else: whatever
      So we've stripped out all the build-depends but we keep everything else,
      including of course the "buildable: False".
  20. 11 Nov, 2016 1 commit
  21. 09 Nov, 2016 1 commit
  22. 08 Nov, 2016 1 commit
  23. 06 Nov, 2016 1 commit
  24. 05 Nov, 2016 2 commits
  25. 04 Nov, 2016 1 commit
  26. 02 Nov, 2016 1 commit
  27. 01 Nov, 2016 1 commit