June 2009 - cabal-devel

patch applied (cabal): follow change in System.Posix.Internals.c_open
by Simon Marlow 23 Jun '09

23 Jun '09

Mon Jun 22 06:36:54 PDT 2009 Simon Marlow <marlowsd(a)gmail.com> * follow change in System.Posix.Internals.c_open Ignore-this: d2c775473d6dfb1dcca40f51834a2d26 M ./Distribution/Compat/TempFile.hs -1 +8 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090622133654-12142-2c3cb8f3…

1 0

patch applied (cabal): update to work with the new GHC IO library internals (fdToHandle)
by Simon Marlow 23 Jun '09

23 Jun '09

Fri Jun 12 02:53:46 PDT 2009 Simon Marlow <marlowsd(a)gmail.com> * update to work with the new GHC IO library internals (fdToHandle) Ignore-this: 2697bd2b64b3231ab4d9bb13490c124f M ./Distribution/Compat/TempFile.hs +4 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090612095346-12142-95307465…

1 0

QuickCheck versions and 'cabal install'
by Stephen Blackheath [to cabal-devel] 15 Jun '09

15 Jun '09

All, I'm getting a lot of this kind of problem now that a new major version of QuickCheck has come out... blackh@amentet:~/src/projectx$ cabal install Resolving dependencies... cabal: dependencies conflict: Crypto-4.2.0.1 requires QuickCheck ==1.2.0.0 however QuickCheck-1.2.0.0 was excluded because QuickCheck-2.1.0.1 was selected instead QuickCheck-1.2.0.0 was excluded because test-framework-quickcheck2-0.2.2 requires QuickCheck >=2.1.0.0 QuickCheck-1.2.0.0 was excluded because ProjectX-0.1 requires QuickCheck >=2.1 It isn't practical to fix this properly - That would require lots of work upgrading quickcheck on all dependent packages. (Crypto-4.2.0.1 is my hacked version of Crypto-4.2.0 with a closed upper version limit to prevent it forcing QuickCheck-2.* which won't compile.) Is there a better solution to this problem? Should a package maintainer have the right to choose an old version of QuickCheck, or should cabal's policy force all package maintainers to upgrade (preferably all on the same day)? Steve

2 2

Including object files in Cabal packages
by C Rodrigues 15 Jun '09

15 Jun '09

Hi, It looks like my last post to the list got messed up somehow. I want to build a Cabal package that contains some Haskell files and one C++ file, which contains C wrappers around C++ code. I would like to compile the C++ file with a makefile, and do everything else (build, install, register, unregister) through Cabal. However, Distribution.Simple.Build.build will only build and link HS and C files; there's no way to link object files into the library. Is there a reason not to add this feature? Where should the list of object files go? I can add it as a new field of BuildInfo, or make it another parameter of build. -Chris _________________________________________________________________ Windows Live™ SkyDrive™: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009

2 2

[Hackage] #435: ban upwardly open version ranges in dependencies on base
by Hackage 15 Jun '09

15 Jun '09

#435: ban upwardly open version ranges in dependencies on base ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- This is wrong! {{{ build-depends: base }}} This is still wrong! {{{ build-depends: base >= 3 }}} Each major release of the base package breaks most packages. Packages should specify an upper bound on the base version. Eg: {{{ build-depends: base >= 3 && < 4 }}} or equivalently: {{{ build-depends: base == 3.* }}} Cabal should check for this and suggest a sensible upper version on the base package, given that we know that base follows the package version policy. Note this is a special case for base but in general we should do this for all packages that opt-in to the versioning policy (see #343). Doing it for all such packages is a medium term goal. Doing it for base is quick and easy and has a lot of immediate benefits for the next release of base. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/435> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 9

patch applied (cabal): Describe the autoconfUserHooks option more accurately in the user guide
by Duncan Coutts 14 Jun '09

14 Jun '09

Sun Jun 14 12:14:00 PDT 2009 Duncan Coutts <duncan(a)haskell.org> * Describe the autoconfUserHooks option more accurately in the user guide M ./doc/Cabal.xml -6 +9 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090614191400-adfee-8a43f78b…

1 0

patch applied (cabal): Fix && entity refs in doc xml
by Duncan Coutts 14 Jun '09

14 Jun '09

Sun Jun 14 12:12:30 PDT 2009 Duncan Coutts <duncan(a)haskell.org> * Fix && entity refs in doc xml M ./doc/Cabal.xml -1 +1 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090614191230-adfee-56a96ea1…

1 0

patch applied (cabal): documentation update: add a description of the syntax for 'compiler' fields in .cabal files
by Duncan Coutts 14 Jun '09

14 Jun '09

Wed Jun 10 12:45:50 PDT 2009 Brent Yorgey <byorgey(a)cis.upenn.edu> * documentation update: add a description of the syntax for 'compiler' fields in .cabal files M ./doc/Cabal.xml +17 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090610194550-1e371-fc8140e4…

1 0

patch applied (cabal-branches/cabal-install-0.6): Now supporting explicit --user or --global switches in bootstrap.sh with usage feedback for bad args
by Duncan Coutts 14 Jun '09

14 Jun '09

Sat Jun 13 08:09:58 PDT 2009 Dino Morelli <dino(a)ui3.info> * Now supporting explicit --user or --global switches in bootstrap.sh with usage feedback for bad args Ignore-this: 490a4fcdd5bc1940d6f32d71b0a042a5 This change was adapted from work submitted to the cabal-devel mailing list by Jason Dusek. M ./bootstrap.sh -1 +24 View patch online: http://darcs.haskell.org/cabal-branches/cabal-install-0.6/_darcs/patches/20…

1 0

patch applied (cabal-branches/cabal-install-0.6): add message to 'package not found' error advising to run 'cabal update'. (#497)
by Duncan Coutts 14 Jun '09

14 Jun '09

Thu Jun 11 10:12:33 PDT 2009 Brent Yorgey <byorgey(a)cis.upenn.edu> * add message to 'package not found' error advising to run 'cabal update'. (#497) M ./Distribution/Client/IndexUtils.hs -1 +2 View patch online: http://darcs.haskell.org/cabal-branches/cabal-install-0.6/_darcs/patches/20…

1 0