- cabal-devel - Haskell.org

patch applied (cabal): "Don't use Prelude.catch"
by Duncan Coutts 24 May '11

24 May '11

Tue May 24 06:19:37 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Don't use Prelude.catch It has been deprecated in ghc-7.2 and ghc builds core libs with -Werror so we have to comply. M ./Distribution/Simple/Utils.hs -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Simpler flat (no sections) parsing for installed package info files"
by Duncan Coutts 24 May '11

24 May '11

Tue May 24 06:20:59 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Simpler flat (no sections) parsing for installed package info files Otherwise we cannot use '{' '}' chars in field contents, as they get interpreted as layout syntax. We want this for things like: library-dirs: ${pkgroot}/../libfoo/ M ./Distribution/InstalledPackageInfo.hs -2 +2 M ./Distribution/ParseUtils.hs -3 +23 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Do a sanity check on the HookedBuildInfo"
by Duncan Coutts 24 May '11

24 May '11

Wed May 18 05:33:31 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Do a sanity check on the HookedBuildInfo Fixes ticket #844. Previously the function that merged the HookedBuildInfo into the PackageDescription would add a library section even if none previously existed. Now we generate an error message if the HookedBuildInfo contains info for non-existant components (libs/exes), e.g: Setup: The buildinfo contains info for a library, but the package does not have a library. M ./Distribution/PackageDescription.hs -5 +1 M ./Distribution/Simple.hs -2 +28 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

darcs patch: Add missing space in QA message
by haskell＠benmachine.co.uk 23 May '11

23 May '11

1 patch for repository http://darcs.haskell.org/cabal: Mon May 23 20:45:34 BST 2011 haskell(a)benmachine.co.uk * Add missing space in QA message

1 0

patch applied (cabal): "Fix the GHC HEAD build: Don't use deprecated catch function"
by Ian Lynagh 23 May '11

23 May '11

Tue Apr 26 16:20:15 PDT 2011 Ian Lynagh <igloo(a)earth.li> * Fix the GHC HEAD build: Don't use deprecated catch function We could make this conditional, to support old GHC versions, but I don't think it is worth the cost to support 6.8. By the time this Cabal is released, you will need at least 6.12 (if not higher) to build the GHC it comes with. M ./Distribution/Simple/Build/PathsModule.hs -2 +5 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

3 4

patch applied (cabal-install): "Fix formatting of cabal init BSD copyright declaration" and 5 others
by Duncan Coutts 21 May '11

21 May '11

Sun May 15 09:38:22 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Fix formatting of cabal init BSD copyright declaration M ./Distribution/Client/Init/Licenses.hs -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi… Mon May 16 01:34:29 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Generate lower case field names in cabal init M ./Distribution/Client/Init.hs -22 +22 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi… Mon May 16 17:20:50 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Add a cabal init question about whether to generate comments Users will typically only want this the first time they use cabal init. M ./Distribution/Client/Init.hs +21 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi… Mon May 16 17:23:02 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Adjust the cabal init interactive prompt string M ./Distribution/Client/Init.hs -3 +3 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi… Mon May 16 17:31:27 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Adjust the initial comment in cabal files generated by cabal init Use slightly longer lines and a somewhat more terse comment. Also use a new shorter and hopefully stable URL for the user guide. M ./Distribution/Client/Init.hs -3 +11 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi… Sat May 21 15:52:03 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * cabal init: various UI tweaks and changes to the generated .cabal files - Add a default "(none)" option for license and category. There are now no questions with no default except for the lib/exe question. For throwaway packages user can just keep hitting enter and get something sensible. - Prune the list of suggested licenses (remove unversioned GPL, LGPL) - Don't include extra-source-files or build-tools when they would be empty - Improve the wording of the generated documentation for lib/exe fields M ./Distribution/Client/Init.hs -30 +48 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi…

1 0

cabal user's guide comment
by Jake Penton 19 May '11

19 May '11

Greetings. What is a package? The reason I ask this question is stated below. If I am posting to the wrong list, let me know. Also, my tone by be slightly abrasive: I am rather frustrated. If I have misread the Cabal user's guide, or am otherwise have my head up my butt, feel free to let me know. Also if I can help (which I doubt, as a beginner) tell me how. My work involves becoming reasonably accomplished in haskell, at which I am a relative beginner. As it is important to be able to use a language in its natural ecosystem, I sat down yesterday to study packages, Cabal, and ghc-pkg. I found this to be rather hard going, mostly because of the documentation - particularly the Cabal user's guide. I appreciate the fact that one of more people went to considerable effort to compose the user's guide, which I get for free. However, I feel that editorial improvements are in order. I find the user's guide unhelpful for several reasons, but I shall only point out one thing in this post: The user's guide fails to provide, early on, information that is IMHO essential to a clear understanding of cabal: What IS a package, i.e. what does the physical implementation of a package look like? The user's guide dances all around this. It mentions the "aims" of cabal, that it provides interfaces, that "developers write packages", that "users install Cabal packages", etc. Under the subheading "Packages" the user's guide says that a "package is the unit of distribution", etc. Ok.... The first hint that a package might possibly be implemented as a hierarchy of directories/files is under the subheading "Creating a package", which makes reference to adding files to the root directory of a package. If that is what a package is (which I remain unsure about) this is too little information, and far too late. To add to the confusion, the examples of packages given in this subsection are NOT examples of packages. They are displays of some kind of file or other - a package description file, or something - whatever a .cabal file might be. In summary, I think the user's guide stands in need of a substantial rewrite. Thanks. - Jake -

6 6

[Hackage] #844: Cabal reports "cabal: internal error: the package contains a library but there is no corresponding configuration data" when there exists no library in the cabal file
by Hackage 18 May '11

18 May '11

#844: Cabal reports "cabal: internal error: the package contains a library but there is no corresponding configuration data" when there exists no library in the cabal file ----------------------------+----------------------------------------------- Reporter: fushunpoon | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: library configuration data Difficulty: normal | Ghcversion: Platform: Mac OS | ----------------------------+----------------------------------------------- When trying to build my test project to play with SDL, I encountered the following message: "cabal: internal error: the package contains a library but there is no corresponding configuration data" on the following cabal file: even though my project cabal file specifies no libraries. Surely either this is an erroneous message or there is something wrong with the logic in cabal. Note that 'configure' and 'sdlexprs.buildinfo.in' exist as files, and they are attached with this post. ------------------------------------------------------ Name: sdlexprs Version: 0.1 Synopsis: Just some hacks using SDL! License: LGPL License-file: LICENSE Author: <<my-name>> Category: Graphics Build-type: Configure Extra-source-files: configure,sdlexprs.buildinfo.in Cabal-version: >=1.2 Executable test -- Specify the source directory here Hs-source-dirs: src -- .hs or .lhs file containing the Main module. Main-is: SDLWrapper.hs -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/844> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

Re: [Hackage] #655: for every install there should be an uninstall
by Hackage 18 May '11

18 May '11

#655: for every install there should be an uninstall ---------------------------------+------------------------------------------ Reporter: nr | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: uninstall Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Comment(by duncan): Replying to [comment:3 nr]: > This is still an issue. I am having a dependency problem with pads- haskell-0.2 and haskell-src-meta-0.4. haskell-src-meta-0.4 depends on haskell-src-exts in the range 1.6 to 1.0. But with haskell-src-exts-1.9, pads-haskell will not build. With haskell-src-exts-1.10.2, pads-haskell will build. Ok, so if I understood correctly we have: pads-haskell-0.2: depends on both haskell-src-meta and haskell-src-exts >= 1.10 haskell-src-meta-0.4: depends on haskell-src-exts >= 1.0 && < 1.9 Which is not solvable because their constraints on haskell-src-exts are inconsistent. One or other package would need to be modified so that they can agree on a common version of haskell-src-exts. If this is really the situation then no amount of installing and uninstalling will help. But I don't think it is the situation, looking on hackage it says that haskell-src-meta-0.4 depends on haskell-src-exts >= 1.6 && < 1.11. > My machine has *both* versions of haskell-src-exts. That's fine, but in the solution there can only be one instance of each package. > But I cannot add the higher dependency to pads-haskell.cabal without extensive bleating. There is clearly an underlying dependency problem here that ought to be addressed, but my immediate concern is to get software to build. If 'cabal uninstall' existed, I could uninstall the older packages and continue. As it is, the only way I know to make progress is to remove all of ~/.cabal and start over. Not a good model. No, I don't understand. If removing packages would help solve the situation then the above description of the version constraints cannot be right. If the situation has a straightforward solution you should be able to do: {{{ $ cd pads-haskell/ $ cabal install --dry-run }}} And it'll replan everything to try and find some combination of versions that works. The sovler is quite happy to reinstall things to achieve a solution. It sounds to me like you've been installing individual packages manually and trying to construct a solution that way. The far easier approach is using `cabal install --dry-run` to construct the whole solution in one go, and if necessary adding `--constraint=` flags to guide the solver, e.g. `--constraint="haskell-src-exts >= 1.10"`. Note also, that this dependency issue is mostly orthogonal to the lack of uninstall feature. For finding solutions it doesn't really matter what is currently installed. It is also possible to eliminate registered packages using ghc-pkg unregister. A cabal uninstall feature would just add recovering the disk space. (Not that that is not important, but is is an independent issue from dependency solving.) Overall, I think we need more clarity on the situation you're looking at and what you've been trying. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/655#comment:6> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #655: for every install there should be an uninstall
by Hackage 18 May '11

18 May '11

#655: for every install there should be an uninstall ---------------------------------+------------------------------------------ Reporter: nr | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: uninstall Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Comment(by benmachine): haskell-src-meta is my package – and it should build with haskell-src- exts-1.10.2. Maybe try reinstalling haskell-src-meta (although that might break anything else that depends on it). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/655#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0