[Hackage] #179: support GHC's main-is extension

[Hackage]

#179: support GHC's main-is extension
----------------------------+-----------------------------------------------
  Reporter:  duncan         |        Owner:          
      Type:  enhancement    |       Status:  reopened
  Priority:  low            |    Milestone:  _|_     
 Component:  Cabal library  |      Version:  1.2.2.0 
  Severity:  normal         |   Resolution:          
  Keywords:                 |   Difficulty:  normal  
Ghcversion:  6.4.2          |     Platform:  Linux   
----------------------------+-----------------------------------------------

Comment(by Evi1M4chine):

 Replying to [comment:23 cjs]:[[BR]]
 I always thought of it like this:

  * The `--main-is` for a build target doesn’t change.
  * Every build target should have its own separate build directory.
  * If `--main-is` ''is'' changed, that invalidates the object file that
 was previously set as main, causing it to get deleted.
  * As early as possible, it is checked that there can always be just one
 module that has a program entry point.

 Those rules would prevent the problem, no?

 P.S.: Aren’t universal binaries executables with two program entry points,
 where the correct one for the arch is chosen by the OS?

-- 
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/179#comment:25>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects