> >> Remember: Cabal isn't only the build infrastructure, it's also the
> >> metadata format that tools like Hackage use. If you decide to combine data
> >> and code, you will no longer be able to manipulate the data with another
> >> tool.
> Visual Haskell, HackageDB, cabal2rpm, and dh_haskell are all tools
> that read the .cabal file and perform operations based on the package
> metadata. These tools would have to be Haskell interpreters if they
> wanted to read a .hs file and derive the package description from
> that.
Then the way to go would be:
add a target "create-editor-readable-package-description".
So still now reason to do this work on your own..
This is not really a pro for cabal files IMHO.
Marc
_______________________________________________
cabal-devel mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cabal-devel
