May 2008 - cabal-devel

patch applied (cabal-branches/cabal-1.2): Fix hscolour code so it only outputs the css once per-lib or exe
by Ian Lynagh 31 May '08

31 May '08

Fri Dec 7 05:03:09 PST 2007 Duncan Coutts <duncan(a)haskell.org> * Fix hscolour code so it only outputs the css once per-lib or exe Rather than for every module in the lib. Tidy the code up a little too. M ./Distribution/Simple/Haddock.hs -10 +11 View patch online: http://darcs.haskell.org/cabal-branches/cabal-1.2/_darcs/patches/2007120713…

1 0

patch applied (cabal-branches/cabal-1.2): Add -framework arguments when linking executables.
by Ian Lynagh 31 May '08

31 May '08

Mon Dec 10 09:40:56 PST 2007 judah.jacobson(a)gmail.com * Add -framework arguments when linking executables. M ./Distribution/Simple/GHC.hs +1 View patch online: http://darcs.haskell.org/cabal-branches/cabal-1.2/_darcs/patches/2007121017…

1 0

patch applied (cabal-branches/cabal-1.2): Use a default HsColour CSS if available
by Ian Lynagh 31 May '08

31 May '08

Thu Dec 6 06:59:37 PST 2007 Duncan Coutts <duncan(a)haskell.org> * Use a default HsColour CSS if available Supported in HsColour 1.9 and later M ./Distribution/Simple/Haddock.hs -8 +11 View patch online: http://darcs.haskell.org/cabal-branches/cabal-1.2/_darcs/patches/2007120614…

1 0

patch applied (cabal-branches/cabal-1.2): make rawSystemStdout put its temp files in the temp dir rather than cwd
by Ian Lynagh 31 May '08

31 May '08

Sun Dec 2 14:06:20 PST 2007 Duncan Coutts <duncan(a)haskell.org> * make rawSystemStdout put its temp files in the temp dir rather than cwd Should fixe reported wierdness with finding program version numbers M ./Distribution/Simple/Utils.hs -2 +4 View patch online: http://darcs.haskell.org/cabal-branches/cabal-1.2/_darcs/patches/2007120222…

1 0

patch applied (cabal-branches/cabal-1.2): Workaround import bug in nhc98
by Ian Lynagh 31 May '08

31 May '08

Fri Nov 23 13:00:09 PST 2007 Duncan Coutts <duncan(a)haskell.org> * Workaround import bug in nhc98 Cabal can now build using itself and nhc98 M ./Distribution/Simple/SetupWrapper.hs -1 +1 View patch online: http://darcs.haskell.org/cabal-branches/cabal-1.2/_darcs/patches/2007112321…

1 0

[Hackage] #287: make better use of existing build/failure reports (provide stats, alert authors)
by Hackage 30 May '08

30 May '08

#287: make better use of existing build/failure reports (provide stats, alert authors) --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | --------------------------------+------------------------------------------- the hackage package list ought to list successful and failed builds (simply a list of compiler versions, each one green or red, depending on success, with direct link to build/failure log; this would fit into the one-line-per-package format) for each entry, and report them to package authors/maintainers (either via direct email or via a daily summary report on a list which all maintainers are subscribed to). build failures currently seem to be created automatically where package authors may not notice them? at least, that would explain things like (just examples of things i happened to have looked at, no offence intended;-) - hint: advertised to work with ghc 6.8.x on the same package page that lists a build failure for ghc-6.8 - haskell-src-exts: lists a build failure for ghc-6.8 the first is probably a too optimistic cabal version spec, the second is a haddock issue. but that makes two out of two for package i looked up recently.. provide cross-package index of builds/failures, so that one might see trends (cabal issues, base package issues, bytestring issues, next big thing issues,..) and statistics(how many hackage packages fail/build, which compiler/cabal/haddock versions are successful for the largest number of packages, etc.)? at the moment, i fully expect this to reflect just as many infrastructure issues as package issues, but that only makes it more important (it is hard to blame package authors if the infrastructure and dependencies keep changing under their feet, or if the tools keep them from providing failure-free packages). Ross provided these rough figures: .. here are some rough figures on failures (for the latest version of each package): 7 configure: prerequisite packages missing or not built 22 configure: other (usually a custom Setup.hs) 6 build: header file for some C library not found on the build system 46 build: a package dependency was not listed (often a base split issue) 14 build: a module was omitted from the package 38 build: other 22 haddock failure 4 install failure It is surprising how many would surely have failed on the maintainer's machine if they had been tested. Duncan points out: It's harder than it looks. The build results from the server builds itself are not very accurate reflections of the real status. That's partly why we do not yet attempt to email maintainers about the results. For example the fact that the build server does not have most C libs installed means that lots of FFI binding packages and all their dependents fail. It also suffers from the diamond dep problem. Also it only reflects one particular operating system and configuration of each package. The plan is to get build results from users. Though then we have to do some statistical analysis to discover if a package works with various versions of compilers and on different OSs etc. http://hackage.haskell.org/trac/hackage/ticket/184 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/287> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #286: have alphabetical sorted package list as well as categorized one
by Hackage 30 May '08

30 May '08

#286: have alphabetical sorted package list as well as categorized one --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | --------------------------------+------------------------------------------- the hackage package list ought to have a link to an alphabetically sorted variant (i often know the package name, but not the likely categories, so i tend to 'search' on that page..). even after hoogle for search, it'd be nice (and probably easy to arrange) to be able to browse both by category and by name. Duncan: The longer term plan is to use hoogle as the primary interface so it can search on package name, package meta-data and of course the content, api and docs. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/286> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

patch applied (cabal-install): As a heuristic, use topological order for the order of package choices
by Duncan Coutts 30 May '08

30 May '08

Fri May 30 11:44:37 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * As a heuristic, use topological order for the order of package choices The general case in exploring the state space is that we have a set of choices (package names) and for each choice we have a number of versions of that package we could pick. If there's only one version of a package then we make that choice first. Otherwise we have to pick some package and select one of the available versions. The question is which package should we make a choice for first? Previously we picked completely arbitrarily. Surprisingly this actually works pretty well. An improvement is to pick packages in topological order. This works better because it allows dependencies from earlier choices to constrain our later choices. M ./Hackage/Dependency/TopDown.hs -19 +86 M ./Hackage/Dependency/TopDown/Types.hs -3 +17 M ./cabal-install.cabal -1 +1 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080530184437-adfee-…

1 0

patch applied (cabal-install): Rearrange and tidy bits of the topdown resolver
by Duncan Coutts 30 May '08

30 May '08

Fri May 30 10:03:06 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Rearrange and tidy bits of the topdown resolver M ./Hackage/Dependency/TopDown.hs -19 +30 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080530170306-adfee-…

1 0

patch applied (cabal-install): Switch install to use resolveDependenciesWithProgress
by Duncan Coutts 30 May '08

30 May '08

Fri May 30 10:01:02 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Switch install to use resolveDependenciesWithProgress And show progress messages at verbosity level 2. M ./Hackage/Fetch.hs -1 M ./Hackage/Install.hs -6 +9 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080530170102-adfee-…

1 0