Changes between Version 5 and Version 6 of Commentary/Packages/PackageMountingProposal


Ignore:
Timestamp:
Oct 30, 2006 8:03:47 AM (9 years ago)
Author:
Frederik
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Commentary/Packages/PackageMountingProposal

    v5 v6  
    3737}}}
    3838
    39 (so the imported namespace would appear as {{{Graphics.Unix.X11.Types}}}, {{{Graphics.Unix.X11.Xlib}}}, etc.)
     39(so the imported namespace would appear as {{{Graphics.Unix.X11.Types}}}, {{{Graphics.Unix.X11.Xlib}}}, etc.) Note that the intention is for each {{{-package-base}}} option to refer to the package specified in the preceding {{{-package}}} option, so to give package {{{PACKAGE}}} a mount point of {{{BASE}}} we use the syntax
    4040
    41 or
     41{{{
     42  ghc ... -package PACKAGE -package-base BASE ...
     43}}}
     44
     45Ideally one would also be able to link to two different versions of the same package, at different mount points:
    4246
    4347{{{
     
    4751(yielding {{{NewX11.Types}}}, {{{NewX11.Xlib}}}, ...; {{{OldX11.Types}}}, {{{OldX11.Xlib}}}, ...)
    4852
    49 However, usually the default mount point would be used. Additionally, Cabal syntax should be extended to support mounting. I would suggest that the optional mount point should appear after a package in the Build-Depends clause of a Cabal file:
     53However, usually the default mount point would be sufficient, so most users wouldn't have to learn about {{{-package-base}}}.
     54
     55Additionally, Cabal syntax should be extended to support mounting. I would suggest that the optional mount point should appear after a package in the Build-Depends clause of a Cabal file:
    5056
    5157{{{