- cabal-devel - Haskell.org

patch applied (cabal-branches/cabal-1.4): Filter out the Paths_pkgname file in sdist
by Duncan Coutts 12 Jun '08

12 Jun '08

Thu Jun 12 02:18:10 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Filter out the Paths_pkgname file in sdist Fixes ticket #187 finally (I hope). M ./Distribution/Simple/SrcDist.hs -11 +22 View patch online: http://darcs.haskell.org/cabal-branches/cabal-1.4/_darcs/patches/2008061209…

1 0

patch applied (cabal): Lift the restriction that libraries must have exposed-modules
by Duncan Coutts 12 Jun '08

12 Jun '08

Thu Jun 12 02:29:24 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Lift the restriction that libraries must have exposed-modules This allows libs that have only private modules or C code. This might be used to make libs that have non-exposed modules and only export C APIs. It could also be used to make packages that consist only of C code. That might be useful for bindings where it may make sense to split the C and Haskell code into separate packages. M ./Distribution/PackageDescription/Check.hs -5 +1 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080612092924-adfee-a737428f…

1 0

patch applied (cabal): Use the standard autogenModulesDir rather than a local copy
by Duncan Coutts 12 Jun '08

12 Jun '08

Thu Jun 12 02:28:55 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Use the standard autogenModulesDir rather than a local copy M ./Distribution/Simple/Build.hs -5 +1 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080612092855-adfee-8a8dbc62…

1 0

patch applied (cabal): Fix the register --gen-pkg-config flag
by Duncan Coutts 12 Jun '08

12 Jun '08

Thu Jun 12 02:24:25 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Fix the register --gen-pkg-config flag When specified without any file name it is supposed to use a default file name rather than be ignored completely. M ./Distribution/Simple/Register.hs -3 +4 M ./Distribution/Simple/Setup.hs -1 +1 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080612092425-adfee-cff3112f…

1 0

patch applied (cabal): Filter out the Paths_pkgname file in sdist
by Duncan Coutts 12 Jun '08

12 Jun '08

Thu Jun 12 02:18:10 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Filter out the Paths_pkgname file in sdist Fixes ticket #187 finally (I hope). M ./Distribution/Simple/SrcDist.hs -11 +22 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080612091810-adfee-f45d73d3…

1 0

[Hackage] #187: Paths_pkgname module is hard to use in a library
by Hackage 12 Jun '08

12 Jun '08

#187: Paths_pkgname module is hard to use in a library ------------------------------+--------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.1 Platform: Linux | ------------------------------+--------------------------------------------- Most users of the auto-generated {{{Paths_pkgname}}} module are programs. With GHC at least they can get away with not specifying the {{{Paths_pkgname}}} in the {{{Other-Modules}}} field. Get away with in the sense that it does not lead to linker errors because {{{ghc --make}}} does dependency chasing and links in all the necessary .o files. However for a library you must specify every module in {{{Exposed- Modules}}} or {{{Other-Modules}}} or one does get linker errors when you try to use the packages. That's because the missing module's .o files will not have been included in the library .a archive. See bug #128. So for a library one must specify {{{Other-Modules: Paths_pkgname}}} but then of course Cabal cannot find that module since it is not in the normal source directories but in {{{dist/build/autogen}}}. So people have to hack around it by adding {{{dist/build/autogen}}} to the {{{Hs-Source-Dirs}}} field. Obviously that's rather unsatisfactory. Probably the right solution is for Cabal to automatically add that directory to the end of the source dir search path. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/187> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #285: hackage trac should permit registration
by Hackage 11 Jun '08

11 Jun '08

#285: hackage trac should permit registration ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: miscellaneous | Version: Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- hackage trac does not seem to have a "register" option (compare hackage trac with ghc trac). individual logins are nice because: - gives individual rather than anonymous reporters - one place less to support spam email harvesters (account name instead of full email address) - "register" is always there, hence easy to find, unlike the hint hidden on the trac home page that hackage is still abusing the haskell' trac.. (might lower the barrier to file report/suggestion tickets) Duncan comments: We used to have that and got horribly spammed. Apparently for the ghc trac they've worked out how to do that without getting spammed so presumably we could do the same. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/285> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

Re: [Hackage] #58: allow darcs repo to be specified in cabal file
by Hackage 11 Jun '08

11 Jun '08

#58: allow darcs repo to be specified in cabal file ----------------------------+----------------------------------------------- Reporter: ijones | Owner: Type: enhancement | Status: new Priority: high | Milestone: Cabal-1.6 Component: Cabal library | Version: Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.2.1 | Platform: Linux ----------------------------+----------------------------------------------- Changes (by duncan): * milestone: Cabal-1.4 => Cabal-1.6 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/58#comment:9> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

What are hookedPrograms for?
by Alistair Bayley 11 Jun '08

11 Jun '08

I'm looking at an example Duncan gave for Takusen's setup + .cabal: http://hpaste.org/6279 ... and do not understamd what hookedPrograms is all about. Can someone enlighten me? FWIW, my goal is to either locate or run some programs during the configure stage, and use the results (locating a program gives a directory, running a program gives directories printed on stdout) to modify the extraLibDirs and includeDirs in BuildInfo. I've been browsing the 1.3.12 sources, but no epiphany yet... Alistair

2 1

patch applied (cabal-install): Take the the flag assignment into account in the resolver
by Duncan Coutts 10 Jun '08

10 Jun '08

Tue Jun 10 16:52:12 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Take the the flag assignment into account in the resolver so it now actually works to say: $ cabal install foo -fbar M ./Hackage/Dependency/TopDown.hs -16 +25 M ./Hackage/Dependency/TopDown/Types.hs -1 +2 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080610235212-adfee-…

1 0