August 2008 - cabal-devel

patch applied (cabal): Fix spelling of compatibility
by Duncan Coutts 18 Aug '08

18 Aug '08

Mon Aug 18 12:49:51 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Fix spelling of compatibility At request of gwern who found that it was driving him nuts. M ./Distribution/License.hs -1 +1 M ./Distribution/Simple.hs -2 +2 M ./Distribution/Simple/InstallDirs.hs -1 +1 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080818194951-adfee-a662bcff…

1 0

patch applied (cabal): Minor info and help message improvements
by Duncan Coutts 18 Aug '08

18 Aug '08

Wed Aug 13 05:49:57 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Minor info and help message improvements M ./Distribution/Simple/Install.hs -2 +2 M ./Distribution/Simple/Setup.hs -1 +3 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080813124957-adfee-ffd004ea…

1 0

Re: [Hackage] #89: Sharing of object files between executable builds?
by Hackage 17 Aug '08

17 Aug '08

#89: Sharing of object files between executable builds? ---------------------------------+------------------------------------------ Reporter: bjorn(a)bringert.net | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: Cabal library | Version: Severity: minor | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ---------------------------------+------------------------------------------ Changes (by guest): * cc: gwern0(a)gmail.com (added) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/89#comment:7> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #89: Sharing of object files between executable builds?
by Hackage 17 Aug '08

17 Aug '08

#89: Sharing of object files between executable builds? ---------------------------------+------------------------------------------ Reporter: bjorn(a)bringert.net | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: Cabal library | Version: Severity: minor | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ---------------------------------+------------------------------------------ Comment (by duncan): See also #276. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/89#comment:6> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #276: Add support for convenience libraries
by Hackage 17 Aug '08

17 Aug '08

#276: Add support for convenience libraries ----------------------------+----------------------------------------------- Reporter: rl | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- I'd like to have a package with several binaries which all use a convenience library included in that same package. The convenience library should NOT be installed. For this to work, Cabal needs two things. Firstly, it must allow dependencies within a package such that I could describe the library and have the binaries depend on it. Secondly, it should have an "installable" flag, similar to "buildable". A thing that's not installable would be built but not installed. The same mechanism could be used for package-internal tools. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/276> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #322: API docs should have source links
by Hackage 15 Aug '08

15 Aug '08

#322: API docs should have source links --------------------------------+------------------------------------------- Reporter: bogner | Owner: Type: enhancement | Status: new Priority: high | Milestone: Component: hackageDB website | Version: 1.2.3.0 Severity: normal | Keywords: source, api Difficulty: easy (<4 hours) | Ghcversion: 6.8.2 Platform: | --------------------------------+------------------------------------------- The API docs for packages should have source links, like the ones on haskell.org and local API docs do. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/322> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #324: Deprecate package-url field
by Hackage 15 Aug '08

15 Aug '08

#324: Deprecate package-url field ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- The package-url field was originally supposed to be to tell users where exactly they could find the .tar.gz package for this version of the package. That was from a time before hackage and so now it is redundant because hackage provides the package url. The field is generally unused and when it is used it often just links to the darcs repo or home page. We should deprecate it and suggest people use the homepage url and the new way of specifying a source control repo (see #58). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/324> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #184: cabal-install should report build results to hackage server
by Hackage 15 Aug '08

15 Aug '08

#184: cabal-install should report build results to hackage server ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.4.2 Platform: Linux | ----------------------------+----------------------------------------------- One way to get a lot more testing data on hackage packages is if cabal- install could report back to the hackage server about build successes and failures. This information should be kept by hackage and used to distill information about which platforms configurations a package builds successfully and which it does not. This should provide useful information to developers to enable them to discover problems more quickly and useful information to users. An important consideration is privacy. Users should always have the option to not report anything and any information they report that is kept should not contain identifying information. This is particularly important when it comes to build logs which may contain paths etc. It should be clear to users what information they are reporting to the can decide for themselves if it meets their privacy needs. Since cabal can be used to build private code it is vital that it reports only on packages that were obtained from the hackage server. It is also vital that the information is sent to the correct hackage server. It's possible to set up private hackage server instances and it'd may be useful to collect build information "in house" too. So what information would be helpful? * build success or failure (qualified by what failed, build, docs, tests) * package name and version * hash of .cabal file just to make sure it's the same one we're all talking about and to detect local modifications. * precise versions of dependent packages that the package was built with. * os and arch strings * compiler flavour and version * versions of important build tools * In the case of a build failure, some part of the build log would be helpful. This is the most problematic part from a privacy point of view. This is quite a bit of raw data and we can expect to have many hundreds of such reports for popular packages. How can we distill useful information from this kind of data? I expect we would want to do some statistical analysis where we look for common traits in the results. The data forms a multi-dimensional space of boolean values. By looking down the rows/columns of this space we should be able to identify trends. For example if it always fails with ghc-6.8.x, or always fails on Windows. Excluding those obvious failures we then may be able to say that it does work on mac osx (except ghc-6.8.1) or that it does work with regex-posix-0.92 (except on windows), etc. This should allow us to give a summary saying yes/no to various properties of the environment. For failure cases developers should be able to get access to the more detailed data including build logs. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/184> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

Re: [Hackage] #56: hackageDB should not accept a package if it is not installable
by Hackage 15 Aug '08

15 Aug '08

#56: hackageDB should not accept a package if it is not installable --------------------------------+------------------------------------------- Reporter: ijones | Owner: Type: enhancement | Status: new Priority: normal | Milestone: HackageDB Component: hackageDB website | Version: Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.2.1 | Platform: Linux --------------------------------+------------------------------------------- Changes (by duncan): * milestone: Cabal-1.6 => HackageDB -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/56#comment:6> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #304: cabal-install does not allow tildes in hackage server URIs
by Hackage 15 Aug '08

15 Aug '08

#304: cabal-install does not allow tildes in hackage server URIs ----------------------------------+----------------------------------------- Reporter: nfrisby | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.2 Platform: | ----------------------------------+----------------------------------------- We're using an internal hackage server, and the Hackage.Config.parseRepo function has been a small hurdle. It does not allow tildes in the URL for the repo, yet obtaining a URL without a tilde requires us to participate in some people process. I bounced the request off Lemmih, and he thinks it's just an oversight. I've attached a patch. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/304> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2