Changes between Version 5 and Version 6 of Commentary/Packages/PackageMountingProposal
- Timestamp:
- 10/30/06 00:03:47 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Commentary/Packages/PackageMountingProposal
v5 v6 37 37 }}} 38 38 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 40 40 41 or 41 {{{ 42 ghc ... -package PACKAGE -package-base BASE ... 43 }}} 44 45 Ideally one would also be able to link to two different versions of the same package, at different mount points: 42 46 43 47 {{{ … … 47 51 (yielding {{{NewX11.Types}}}, {{{NewX11.Xlib}}}, ...; {{{OldX11.Types}}}, {{{OldX11.Xlib}}}, ...) 48 52 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: 53 However, usually the default mount point would be sufficient, so most users wouldn't have to learn about {{{-package-base}}}. 54 55 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: 50 56 51 57 {{{
