May 2008 - cabal-devel

Re: [Hackage] #283: install command doesn't install dist/doc/users-guide/
by Hackage 28 May '08

28 May '08

#283: install command doesn't install dist/doc/users-guide/ ----------------------------------------------+----------------------------- Reporter: Misha Aizatulin <avatar(a)hot.ee> | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Resolution: Keywords: | Difficulty: very hard (<1 week) Ghcversion: 6.8.2 | Platform: ----------------------------------------------+----------------------------- Changes (by duncan): * difficulty: normal => very hard (<1 week) Comment: This is part of the wider issue that Cabal does not handle general docs, just haddock docs. This is mostly because documentation is almost completely non-standardised. We know what to do with haddock. For other kinds of documentation it always seems to need custom scripts. The Cabal manual is a case in point, it needs docbook. How do we identify that doc/Cabal.xml is a docbook file? Perhaps we should rename it to doc/Cabal.docbook. If we can identify that it is docbook how do we process it portably? Are there any standard processing tools? Currently we have to use a raw XSLT processor and guess the location of the xslt stylesheet. Similar issues come up for latex, man pages, raw html, plain text files etc. We need to be able to identify them and apply standard build rules. This all works nicely for source files because we use standard conventions. We'll have to do something similar with documentation. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/283#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #196: ability to specify custom args to haddock
by Hackage 27 May '08

27 May '08

#196: ability to specify custom args to haddock ---------------------+------------------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.1 Platform: Linux | ---------------------+------------------------------------------------------ From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293523 {{{ The ability to specify custom args to haddock, which is necessary to do things such as build docs that encompass parts of other packages }}} We can pass extra options to any program via the generic configure --$PROG-options= mechanism however for haddock this is not very useful since we also have to call haddock for another purpose and passing extra options there causes problems. Since the debian bug was filed there are several more feature of the haddock command, perhaps they solve the problem. If not, perhaps the problem could be explained further. What problem are we trying to solve here that would require passing extra options to haddock, and what extra options would one use? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/196> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

Re: [Hackage] #283: install command doesn't install dist/doc/users-guide/
by Hackage 27 May '08

27 May '08

#283: install command doesn't install dist/doc/users-guide/ ----------------------------------------------+----------------------------- Reporter: Misha Aizatulin <avatar(a)hot.ee> | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.8.2 | Platform: ----------------------------------------------+----------------------------- Changes (by guest): * cc: Misha, Aizatulin, <avatar(a)hot.ee> (removed) * reporter: guest => Misha Aizatulin <avatar(a)hot.ee> -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/283#comment:1> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #283: install command doesn't install dist/doc/users-guide/
by Hackage 27 May '08

27 May '08

#283: install command doesn't install dist/doc/users-guide/ ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- When doing install on cabal itself, only the contents of dist/doc/html are copied to their install location. The users guide doesn't get installed. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/283> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

cabal-install uninstall ?
by Henrique Ferreiro García 23 May '08

23 May '08

Hi! I'd like to get involved in haskell development and I think this could be a good start. I don't know how much time I'll have to do this, but if you give me that advice I'll try to implement this functionality. > So as you say, the way to do this would be to generate a list of files > that will be installed. This can be used to later uninstall. > If you want to work on this feature I can provide some advice on how to > implement it. It'll need a bit of work to restructure the install code > so that it actually produces a list of things to install, rather than > just installing them. -- Henrique Ferreiro García <hferreiro(a)udc.es>

2 4

[Hackage] #270: Build executables that can be run "in-place"
by Hackage 22 May '08

22 May '08

#270: Build executables that can be run "in-place" ----------------------------+----------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- It would be nice if Cabal could build executables that could be told where to get their data files (etc), instead of always hard-wiring them to the installation dirs. Perhaps an environmental variable could be used to specify where the data files are. This would enable us to run applications "in-place", i.e. from the source directory directly, which would be useful for test suites, for example. David -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/270> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #277: add data-dir field
by Hackage 22 May '08

22 May '08

#277: add data-dir field ------------------------------+--------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: minor | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.2 Platform: | ------------------------------+--------------------------------------------- Cabal currently looks for data files to install relative to the source directory, giving the package author no possibility to move them into their own directory without cluttering up the cabal file (you end up writing things like {{{data-files: data/foo, data/bar, data/foobar}}}) and the source (where you'll have to include the {{{"data/"}}} prefix in all calls to {{{getDataFileName}}}). The proposal is to add a {{{data-dir}}} field to the package configuration that specifies a single path which is used as a prefix for all data files in the source directory. The location of the installed files is not affected by {{{data-dir}}}. Notes: * It's impossible to change {{{data-dir}}} to take a list of paths without breaking the {{{Paths_foo}}} module interface. * installation of data files will have to copy source files from a different location, ditto for sdist * installed packages don't change. In particular the {{{Paths_foo}}} module doesn't change. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/277> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #174: cabal-install tries to upgrade the base package
by Hackage 21 May '08

21 May '08

#174: cabal-install tries to upgrade the base package ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.6 Platform: Linux | ----------------------------+----------------------------------------------- When using ghc-6.6.x, with some packages, cabal-install tries to upgrade the base package to satisfy dependnecies. This is obviously impossible. The dependency resolution mechanism needs to be taught this fact. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/174> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 7

patch applied (cabal-install): Hide any available base and ghc-prim packages from the dep resolver
by Duncan Coutts 21 May '08

21 May '08

Wed May 21 08:37:00 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Hide any available base and ghc-prim packages from the dep resolver Previously if the base package was available on hackage then the dep resolver might try to upgrade it. Unfortunately that's almost certainly technically impossible at the moment. So now since the dep resolver does not see these available packages it cannot pick them. This should fix ticket #174. M ./Hackage/Dependency.hs -1 +7 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080521153700-adfee-…

1 0

patch applied (cabal-install): Remove the silly failing resolver demo
by Duncan Coutts 21 May '08

21 May '08

Wed May 21 08:36:48 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Remove the silly failing resolver demo M ./Hackage/Dependency.hs -6 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080521153648-adfee-…

1 0