[Hackage] #282: profiling versions of libraries not managed well
#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 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
#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: profiling | Difficulty: normal Ghcversion: 6.8.2 | Platform: ---------------------------------+------------------------------------------ Comment (by duncan): We'll need some way of tracking if the profiling flavour of the libraries are installed. Currently this is not tracked anywhere. GHC only find out they're not installed when it tries to use them. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/282#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: profiling | Difficulty: normal Ghcversion: 6.8.2 | Platform: ---------------------------------+------------------------------------------ Changes (by bos): * cc: bos@serpentine.com (added) Comment: I'd love it if this could be bumped in priority somehow. It can easily take half an hour to chase down the chain of dependencies and rebuild everything if you forgot to install a profiling library, with many redundant attempts at builds along the way. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/282#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: profiling | Difficulty: hard (< 1 day) Ghcversion: 6.8.2 | Platform: ---------------------------------+------------------------------------------ Changes (by duncan): * difficulty: normal => hard (< 1 day) Comment: The best way to increase the priority is to send patches, or persuade someone else to do so. In general, it's not a trivial problem. For each package we'll have to track the bits that are installed and map the config flags to which ones are needed and then update the dependency solver to take those into account. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/282#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: profiling | Difficulty: hard (< 1 day) Ghcversion: 6.8.2 | Platform: ---------------------------------+------------------------------------------ Comment (by guest): This probably needs an extension to ghc-pkg, so that ghc's database can record whether a package is installed with profiling version or not. Then cabal-install's job is easy - it just does the same installed-package query as usual, except with the profiling flag set. (Actually, maybe it is an _easier_ job that usual, because the version numbers of some packages will be fixed by the non-profiled installation, rather than cabal-install having to devise a versioning plan to satisfy all dependencies.) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/282#comment:4 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: profiling | Difficulty: hard (< 1 day) Ghcversion: 6.8.2 | Platform: ---------------------------------+------------------------------------------ Comment (by duncan): See also #425. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/282#comment:5 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: profiling | Difficulty: hard (< 1 day) Ghcversion: 6.8.2 | Platform: ---------------------------------+------------------------------------------ Comment (by duncan): Our current thinking on this issue is that we should track each "way" separately. That is we should register profiling, vanilla and any other ways with ghc-pkg as independent package instances. This needs coordination with ghc since it means a change to the package registration information to include the way. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/282#comment:6 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: profiling | Difficulty: hard (< 1 day) Ghcversion: 6.8.2 | Platform: ---------------------------------+------------------------------------------ Changes (by guest): * cc: chevalier@alum.wellesley.edu (added) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/282#comment:7 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
participants (1)
-
Hackage