July 2010 - cabal-devel

[Hackage] #697: Add "cabal build-dep" command
by Hackage 05 Jan '12

05 Jan '12

#697: Add "cabal build-dep" command ---------------------------------+------------------------------------------ Reporter: igloo | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: major | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ The [http://hackage.haskell.org/trac/ghc/wiki/HackageTesting hackage testing tool] needs a "cabal build-dep" command to work. I had an inadequate patch that was good enough for my experiments (http://osdir.com/ml/cabal-devel@haskell.org/2010-01/msg00029.html) but lack the familiarity with the cabal-install design necessary to implement it properly. Sadly, the patch no longer applies to cabal-install HEAD, and regardless, it would make things a lot easier if it Just Worked out of the box. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/697> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 7

[Hackage] #709: cabal doesn't handle error conditions from getAppUserDataDirectory
by Hackage 05 Jan '12

05 Jan '12

#709: cabal doesn't handle error conditions from getAppUserDataDirectory ----------------------------+----------------------------------------------- Reporter: creswick | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 6.12.1 Platform: Windows | ----------------------------+----------------------------------------------- Distribution.Simple.InstallDirs.defaultInstallDirs fails if getAppUserDataDirectory fails, and it does so with a very uninformative error: {{{ # On Cabal 1.8.0.2: cabal.exe: illegal operation }}} This is a slight regression from the HP 2009 version: {{{ # On Cabal 1.6.0.3: cabal.exe: System.Directory.getAppUserDataDirectory: unsupported operation (unsupported operation) }}} This happens on Windows Vista, in cygwin, when the user doesn't have a windows user directory (eg: c:\users\username ). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/709> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #698: Hayoo! links on Hackage are broken
by Hackage 05 Jan '12

05 Jan '12

#698: Hayoo! links on Hackage are broken --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.6.0.3 Severity: minor | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- The links to Hayoo! on Hackage point to http://holumbus.fh- wedel.de/hayoo/hayoo.html, which is returning a 404 File Not Found error. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/698> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #693: Missing instructions for running Cabal's testsuite
by Hackage 05 Jan '12

05 Jan '12

#693: Missing instructions for running Cabal's testsuite ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- It's not quite clear to me how to get `tests/suite.cabal` to build using an in-place build of Cabal. I played around with passing `--package-db ../dist/package.conf.inplace` to `configure` when configuring `tests/suite.cabal` without success. A `tests/README` file would be very useful. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/693> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 10

[Hackage] #679: Hackage website should obscure email addresses
by Hackage 05 Jan '12

05 Jan '12

#679: Hackage website should obscure email addresses --------------------------------+------------------------------------------- Reporter: jbapple | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- Email addresses on hackage are getting captured by spambots. HackageDB can implement solutions that individual maintainers could not (javascript) or reduce the amount of redundant work maintainers have to do. Leaving the field unprotected discourages maintainers from providing email addresses for contact. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/679> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #676: bash-completion gets confused by alias for rm
by Hackage 05 Jan '12

05 Jan '12

#676: bash-completion gets confused by alias for rm ---------------------------------+------------------------------------------ Reporter: benmachine | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: minor | Keywords: Difficulty: unknown | Ghcversion: 6.12.1 Platform: Linux | ---------------------------------+------------------------------------------ I have an alias for rm defined so that it is by default verbose (alias rm='rm -v' in my bashrc). When I do cabal install has<tab> I get something like: [ben@euler ~]$ cabal install hasbash: bad substitution: no closing "`" in `/tmp/cabal_completion.tD2o8O' It turns out that rm is helpfully going: removed `/tmp/cabal_completion.hb1zbc' and then cabal is trying to use this as part of the completion command - choking on the ` because bash thinks it is part of a substitution. So rm should probably explicitly discard its stdout. While I was there I noticed that "cat" is used redundantly. There's nothing really wrong with this so that part of the patch can be cut I suppose, but I thought it was neater to use bash's input redirection explicitly. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/676> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #677: Error: Couldn't read cabal file "./HDBC/2.2.5/HDBC.cabal"
by Hackage 05 Jan '12

05 Jan '12

#677: Error: Couldn't read cabal file "./HDBC/2.2.5/HDBC.cabal" ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 6.10.4 Platform: Linux | ---------------------------------+------------------------------------------ I recently upgraded cabal-install and started getting this error: $ cabal install HDBC Resolving dependencies... cabal: Couldn't read cabal file "./HDBC/2.2.5/HDBC.cabal" I also get the same error when I try to install one of my own packages that depends on HDBC. I tried changing my HDBC dependency to == 2.2.2 as well as >= 2.2.6, but still get the same error for version 2.2.5. I have cabal-install version 0.6.2 and Cabal version 1.6.0.3. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/677> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #674: Findable extra documentation
by Hackage 05 Jan '12

05 Jan '12

#674: Findable extra documentation ----------------------------+----------------------------------------------- Reporter: jbapple | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I have a cabal package that should include extra documentation in the distribution. This documentation should not be written in Haddock. 1. There should be a field for this analogous to data-files or extra- source-files. The former is too much: the files do not need to be accessed by any Haskell runtime. The latter is not enough: it does not store the extracted files on the system on which the package is installed. 2. There should be a way for humans to find these files without loading up a GHC runtime or using Unix's "find". I suggest "cabal list" also shows, for installed packages with extra data or documentation files installed, where these files can be found. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/674> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #704: sort out design for foreign code in Haskell libraries
by Hackage 09 Nov '10

09 Nov '10

#704: sort out design for foreign code in Haskell libraries ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: task | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Currently we often happily add little bits of C glue code into Haskell packages. This is perfectly reasonably but we also want to be able to do things like linking multiple versions of a Haskell package into a single application. That does not work if the C symbols are visible outside of the package (see #701). It seems reasonable to require that C code in a Haskell package respects the properties that we want for Haskell packages. However we must also allow for libraries that are foreign code and not Haskell libraries at all. For example, the zlib binding package ships a complete copy of the zlib C code for platforms that do not have it natively. Unlike bits of FFI glue code, it is unreasonable to expect to change the zlib code to conform to Haskell library requirements. Perhaps what we need is to explicitly identify foreign libraries and hold them to different (lower) standards compared to Haskell libraries. One idea would be to draw together the features proposed in these tickets: * #276 : support for convenience libraries * #148 : producing foreign libraires The idea with convenience libraries is that a package can have multiple libraries in it, even though at most one can be the library that has exposed modules. Other libraries could be used by executables or the main library in that package. The main purpose is sharing but it could also be a way to separate the requirements of haskell code and foreign code. Producing foreign libraries is about making libraries (usually but not necessarily containing Haskell code) that export a foreign C API and are not intended to be used by other Haskell code. Combining these two features would allow for the zlib example to work ok. We would declare a foreign library with the zlib C code and make the main Haskell binding library depend on it. Note that packages that depend on the binding package would not directly link to the C library (this is significant for shared libs). The key constraint for foreign libraries is that we cannot link more than one version into a single application (because the symbols would clash), where as we may assume that it is perfectly safe to link multiple versions of a Haskell package. Any design must also consider symbol visibility. This is relevant both for shared and static libs. With static libs it is hard to avoid every symbol being globally visible. With shared libs there is greater control over symbol visibility but also the restriction on some systems that each shared lib must resolve all symbol references. This means we must more explicitly identify which libraries import symbols from others. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/704> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

Package Dependency License Checking
by Trevor Elliott 10 Oct '10

10 Oct '10

Hi Everyone, I have started implementing a license compatibility check in Cabal, and was interested in getting some early feedback. The attached patch will, as part of the configure step, check that the dependencies have licenses that are compatible with the license chosen for the package being configured. No errors are thrown as a result of incompatible licenses, though warnings are printed. Thanks, --trevor

2 1