February 2010 - cabal-devel

patch applied (cabal-branches/cabal-1.8): MERGED: Get the correct value of $topdir on Windows with GHC 6.12.1
by Ian Lynagh 04 Feb '10

04 Feb '10

Thu Feb 4 05:29:38 PST 2010 Ian Lynagh <igloo(a)earth.li> * MERGED: Get the correct value of $topdir on Windows with GHC 6.12.1 Ian Lynagh <igloo(a)earth.li>**20091230204613 This doesn't full merge the patch, as partly it changed an interface in order to refactor. M ./Distribution/Simple/GHC.hs -2 +7 View patch online: http://darcs.haskell.org/cabal-branches/cabal-1.8/_darcs/patches/2010020413…

1 0

Upgrading to cabal-install-0.8.0: messages on Windows
by José Pedro Magalhães 02 Feb '10

02 Feb '10

Hello all, When updating my cabal-install to work with ghc-6.12, I got: > cabal configure > cabal: This version of the cabal program is too old to work with ghc-6.12+. > You will need to install the 'cabal-install' package version 0.8 or higher. > If you still have an older ghc installed (eg 6.10.4), run: > $ cabal install -w ghc-6.10.4 'cabal-install >= 0.8' > > > cabal install -w ghc-6.10.4 'cabal-install >= 0.8' > cabal: "'cabal-install" is not valid syntax for a package name or package > dependency. > > > cabal install -w ghc-6.10.4 "cabal-install >= 0.8" > cabal: Cannot find the program 'ghc' at 'ghc-6.10.4' or on the path > > > cabal install -w c:\ghc\ghc-6.10.4\bin\ghc "cabal-install >= 0.8" > Resolving dependencies... (...) > Then all worked fine. Note that I had ghc-6.12.1 on the PATH and this is Windows XP 64bit. I found the first message rather informative, but unfortunately the command given does not work on Windows in general, as far as I know. For starters, the shell doesn't seem to like single quotes, but moreover, the full path to the ghc binary has to be supplied, as no symbolic links such as "ghc-6.10.4" are available. Perhaps these messages could be updated to be more helpful to Windows users? Cheers, Pedro

1 0

[Hackage] #628: Greencard files are processed incorrectly
by Hackage 01 Feb '10

01 Feb '10

#628: Greencard files are processed incorrectly ----------------------------+----------------------------------------------- Reporter: mpiechotka | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 6.10.1 Platform: | ----------------------------+----------------------------------------------- If I use greencard file (.gc): 1. stub files are created in source directory instead of dist 2. stub files are not compiled PS. Version is 1.8.0.2 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/628> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #89: Sharing of object files between executable builds?
by Hackage 01 Feb '10

01 Feb '10

#89: Sharing of object files between executable builds? ---------------------------------+------------------------------------------ Reporter: bjorn@… | Owner: blackh Type: enhancement | Status: assigned Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.4.2 Platform: Linux | ---------------------------------+------------------------------------------ Comment(by AnttiJuhaniKaijanaho): Replying to [comment:22 duncan]: > For ghc --make you simply get wrong results (it does not track when you change compile options). Which is relevant in sophisticated cases. I'm concerned that cabal makes simple things more complicated than they need to be. > As a design choice (one made long ago) Cabal lets you specify different compile options for the same source file when used in different components. Which is a nice thing to have when you need it. > > What about allowing specifying a list of modules common to all executables? That would help me. (Or, of course, if the "private libraries" are lightweight enough that I just have to list the modules that are included in it, that's good enough.) > > That would be similar though I think I prefer the private library approach, it's a bit more flexible. The "common modules" approach does not work for sharing modules between a library and an executable with ghc because the module need to be compiled differently. Similarly, I'd like a way to specify compilation options (such as warnings) common to all executables. ... Heh. Should I be opening a separate ticket? :) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/89#comment:23> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #627: Nonsense tarball permissions with sdist in Cabal 1.8.0.2
by Hackage 01 Feb '10

01 Feb '10

#627: Nonsense tarball permissions with sdist in Cabal 1.8.0.2 ----------------------------+----------------------------------------------- Reporter: draconx | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Linux | ----------------------------+----------------------------------------------- After upgrading to Cabal 1.8, running './Setup.lhs sdist' in any package is generating tarballs with bizarre permissions: - Every directory has mode 0755. - Every file has mode 0600. In particular, the executable bits from files are lost, and files should be group/world readable. Cabal 1.6 generates correct permissions. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/627> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2