[Hackage] #282: profiling versions of libraries not managed well

Hackage trac at galois.com
Sat May 24 12:26:48 EDT 2008

#282: profiling versions of libraries not managed well
  Reporter:  SamB                |        Owner:           
      Type:  defect              |       Status:  new      
  Priority:  normal              |    Milestone:           
 Component:  cabal-install tool  |      Version:  
  Severity:  normal              |     Keywords:  profiling
Difficulty:  normal              |   Ghcversion:  6.8.2    
  Platform:                      |  
 At the moment, if you want profiling builds of libraries which you have
 already installed, the only way to get them is to unregister and rebuild
 with profiling turned on. This is especially inconvenient when you have a
 program that depends on many different libraries...

 Ideally, I could just add a flag to rebuild a program with profiling,
 regardless of whether I'd installed profiling versions or not...

 Any ideas on how this should be managed? What configurations should be
 allowed? How do we make sure the same library version is used for the
 profiling build as was used for the normal build? When do we just give up
 and make the user figure it out?

Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/282>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects

More information about the cabal-devel mailing list