On Fri, 2009-11-13 at 15:53 -0200, Maurício CA wrote:
This is a package with no library and no executables. That's not supposed to work.
Why shouldn't this be supposed to work? It does install needed files (two include files for hsc2hs), and they do stand for themselves to justify a package of its own.
Header files are associated with a library. If there is no library then nothing gets registered. This is by design.
Doesn't Cabal option 'install-includes' contradicts that?
No. The install-includes field is part of a library or executable section in a .cabal file. It is not global to a package as a whole.
If it's not a library, nothing can depend on it.
But please tell me then where my package fits.
I'm not sure I understand the question. Can you clarify what you mean.
Many libraries I wrote and use depend heavily on it. Versioning in this package is extremely important, as a change in design for any macro would change all names in depending libraries.
I notice that you have changed the package to include a library. Duncan