Meta-cabalizing contributions

[rlaemmel]

Subject to some discussion, we might want to set up a template-based procedure to generate the .cabal files for the contributions, as they appear to be highly regular, which is good. So some sort of script would be run before cabal.

Just an idea.

This sort of relates to the question of factoring code across contributions, except that this is already a more sophisticated instance, as the .cabal files differ of course for the different contributions.

[rlaemmel]

Ok, now that I have seen more examples, I file a more concrete proposal.

Let's discuss it first.

• Name of the tool: 101cabal (for example)
• Location: github repo 101haskell/tools/101cabal
• Programming language: Python
• Input: 101cabal.json
• Output: .cabal

Here is the template

 name:                <name of contribution>
 version:             0.1.0.0
 synopsis:           <headline should be retrieved via discovery service>
 homepage:        <URL to contribution page on 101companies.org>
 license-file:        ???
 author:              <copy from 101cabal.json>
 maintainer:        <copy from 101cabal.json>
 build-type:          Simple
 cabal-version:       >=1.9.2

 library
   exposed-modules:
     <all files in src other than Main.hs>
   build-depends:       <copy from 101cabal.json>
   hs-source-dirs:      src

 test-suite basic-tests
     main-is:           Main.hs
     build-depends:     base, HUnit
     hs-source-dirs:    src
     type:              exitcode-stdio-1.0

Here is how 101cabal.json may look like.

{ 
  author : "Ralf Lämmel",
  maintainer : "rlaemmel@gmail.com",
  depends : "base >=4.4 && < 5.0"
}

Discussion:

• How we plan to use "version" anyway?
• So how do we go about license?
• I guess we need to upgrade the discovery service to include headlines.