This project is mirrored from Pull mirroring updated .
  1. 27 Aug, 2014 1 commit
    • Duncan Coutts's avatar
      Change rep of module re-exports, and do resolution ourselves · a3d3273a
      Duncan Coutts authored
      The initial support for module re-exports relied on ghc-pkg to resolve
      user-specified re-exports to references to specific installed packages.
      This resolution is something that can fail so it's better for Cabal to
      do it during the package configure phase.
      In addition, it is inconvenient in ghc-pkg to be doing this resolution,
      and it just seems fishy as a design. Also, the same ModuleExport type
      was being used both for user-specified source re-exports and also for
      the specific re-exports in the package db.
      This patch splits the type into two: one for source level, and one for
      resolved ones for use in the package db. The configure phase resolves
      one to the other.
      One minor change: it is now possible to re-export a module defined in
      the same package that is not itself exported (ie it's in other-modules,
      rather than exposed-modules). Previously for modules definied in the
      same package they had to be themselves exported. Of course for
      re-exports from other packages they have to be exposed.
  2. 16 Jul, 2014 1 commit
    • Edward Z. Yang's avatar
      Implement "reexported-modules" field, towards fixing GHC bug #8407. · 62450f9a
      Edward Z. Yang authored
      Re-exported modules allow packages to reexport modules from their
      dependencies without having to create stub files.  Reexports of the same
      original module don't count as ambiguous imports when module finding
      occurs.  The syntax is:
          "orig-pkg" OrigName as NewName
      You can omit 'as NewName', in which case it is reexported as the same
      name.  Self referential aliases work too; however, they're only visible
      to packages which depend on this package.
      Left to future work: just provide a module name 'OrigName', where ghc-pkg
      figures out what the source package is.
      Signed-off-by: default avatarEdward Z. Yang <>
  3. 14 Apr, 2014 1 commit
  4. 07 Sep, 2013 1 commit
  5. 25 Jun, 2012 1 commit
    • Duncan Coutts's avatar
      Fix impl of PackageIndex.allPackagesByName · 6192dbf4
      Duncan Coutts authored
      Fixes the problem with generating the haddock documentation contents page for
      all installed packages. Previously we were (accidentally) telling haddock to
      use all versions of each package and haddock would pick the first (lowest
      version). Now we correctly do what we were trying to do all along, which is
      to pick only the highest version of each package.
  6. 23 Oct, 2011 1 commit
  7. 19 Jun, 2011 1 commit
  8. 09 Oct, 2010 1 commit
  9. 29 Nov, 2009 1 commit
  10. 06 Oct, 2009 1 commit
  11. 05 Oct, 2009 1 commit
    • Duncan Coutts's avatar
      Rewrite the PackageIndex again · 15f70a85
      Duncan Coutts authored
      It's a unified index again, rather than one for looking up by an
      InstalledPackageId and one for the source PackageId. The new one
      lets you look up by either. It also maintains the order of
      preference of different installed packages that share the same
      source PackageId. In configure we just pick the first preference.
  12. 22 Aug, 2009 1 commit
  13. 06 Aug, 2009 1 commit
    • Simon Marlow's avatar
      Add a unuque identifier for installed packages (part 3 of 9) · a809635c
      Simon Marlow authored
      This part adds the InstalledPackageIndex type to
      Distribution.Simple.PackageIndex.  Now that packages have a unique
      identifier within a package database, it makes sense to use this as
      the key for looking up installed packages, so InstalledPackageIndex is
      a mapping from InstalledPackageId to InstalledPackageInfo.
      Distribution.Simple.PackageIndex still supports other kinds of package
      mappings: PackageIndex is a mapping from PackageName.
      All the functions in the section "Special Queries" now work on
      InstalledPackageIndex rather than PackageFixedDeps pkg => PackageIndex
  14. 02 Oct, 2008 1 commit
    • Duncan Coutts's avatar
      Relax dependencyInconsistencies to allow the base-3,4 thing · 991e52a4
      Duncan Coutts authored
      Previously we said a package graph was inconsistent if two
      dependencies on the same package name specified different
      versions. Now we say that two such dependencies on different
      versions are ok if there is a direct dependency between those
      two package versions. So if your package graph ends up with
      both base 3 and base 4 in it, then that's ok because base 3
      directly depends on base 4, so we declare it not to be an
      inconsistency. This removes the scary warnings at configure
      time (fixing ticket #366) and also adjusts the invariant and
      assertion of the InstallPlan ADT in cabal-install.
  15. 04 Sep, 2008 1 commit
  16. 30 Aug, 2008 1 commit
    • Duncan Coutts's avatar
      Merge PackageSet and PackageIndex · eea57172
      Duncan Coutts authored
      Have just a single module that provides both the case sensitive and
      insensitive operations. Turns out we hardly use the case insensitive
      operations, and the places where we do are not performance sensitive
      at all. So we use the PackageSet implementation which stores the
      packages case sensitively and tack on the case insensitive operations
      but with linear time implementations rather than log time. For the
      merged module/type name use PackageIndex because that is what older
      released versions exported, so less needless client breakage.
  17. 20 Jul, 2008 1 commit
    • Duncan Coutts's avatar
      Convert from PackageIndex to PackageSet · c6f2d793
      Duncan Coutts authored
      Turns out the feature to do case-insensitive lookups was only
      needed in cabal-install (and only in one little part) and
      elsewhere it causes problems. So use PackageSet instead.
  18. 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.
  19. 14 Jun, 2008 1 commit
  20. 12 Jun, 2008 1 commit
  21. 29 May, 2008 1 commit
  22. 14 May, 2008 5 commits
  23. 06 May, 2008 4 commits
  24. 04 May, 2008 3 commits
  25. 15 Apr, 2008 1 commit
  26. 12 Mar, 2008 1 commit
  27. 07 Mar, 2008 1 commit
  28. 22 Feb, 2008 1 commit
  29. 21 Feb, 2008 1 commit
  30. 20 Feb, 2008 2 commits