On Wed, 18 May 2005, Isaac Jones wrote:
3. Can I access the source of all exposed modules in an installed package to enumerate its external module dependencies and import chase?
Not the source of binary packages, but the .hi files have this information, I believe.
Can I access the .hi files of the hidden modules as well? Do you know how to extract import statements from .hi files?
4. If you have an unpacked package in a directory, is there a path from the cabal file to the relative paths of each file in the package? (so you can point at a repository rather than a tarball and access it via http).
Yeah. You can derive it from the module name plus the hs-source-dirs.
What about other stuff like enclosed C files, makefiles, etc? -Alex- ______________________________________________________________ S. Alexander Jacobson tel:917-770-6565 http://alexjacobson.com