- cabal-devel - Haskell.org

Re: [Hackage] #91: Building executables that use Template Haskell for profiling
by Hackage 15 Aug '08

15 Aug '08

#91: Building executables that use Template Haskell for profiling ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.1.4 Severity: normal | Resolution: Keywords: | Difficulty: easy (<4 hours) Ghcversion: 6.5 | Platform: Linux ----------------------------+----------------------------------------------- Changes (by duncan): * milestone: Cabal-1.6 => Cabal-1.8 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/91#comment:3> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #24: Cabal shouldn't try to build GHCI libs on platforms without GHCI
by Hackage 15 Aug '08

15 Aug '08

#24: Cabal shouldn't try to build GHCI libs on platforms without GHCI ------------------------------------+--------------------------------------- Reporter: jgoerzen(a)complete.org | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: Severity: normal | Resolution: Keywords: | Difficulty: easy (<4 hours) Ghcversion: 6.2.1 | Platform: Linux ------------------------------------+--------------------------------------- Changes (by duncan): * milestone: Cabal-1.6 => Cabal-1.8 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/24#comment:8> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #93: Incorrect permissions on library install
by Hackage 15 Aug '08

15 Aug '08

#93: Incorrect permissions on library install ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.1.4 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Changes (by duncan): * milestone: Cabal-1.6 => Cabal-1.8 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/93#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #212: Overhaul Cabal's testsuite
by Hackage 15 Aug '08

15 Aug '08

#212: Overhaul Cabal's testsuite ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: task | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: very hard (<1 week) | Ghcversion: 6.8.2 Platform: | ----------------------------------+----------------------------------------- The current testsuite based on HUnit is almost completely bitrotted. Anyone who wants to take this on has essentially a completely clean slate to work from. The current system is split into two parts. There are hunit tests in many of the modules guarded by #ifdef DEBUG. Then there are external tests in the `tests/` subdirectory. The #ifdef DEBUG style is annoying since it involves using more CPP than seem really necessary. A couple notes from the old `TODO` file: {{{ ** add a make target or command for tests we know will fail? ** setup test suite to run on --push? ** redirect non-hunit outputs to a file? }}} One possibility that is available to us now that was not before is using the hackage collection as part of a regression test. For example it should always be possible to parse all the `.cabal` files in the index. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/212> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

Re: [Hackage] #42: implement hugs-pkg?
by Hackage 15 Aug '08

15 Aug '08

#42: implement hugs-pkg? ----------------------------+----------------------------------------------- Reporter: ijones | Owner: ross(a)soi.city.ac.uk Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.2.2 | Platform: ----------------------------+----------------------------------------------- Changes (by duncan): * owner: => ross(a)soi.city.ac.uk Comment: So I'm happy with the idea that for hugs and nhc that we do not need a distinct concept of a package database. The package database can coincide with the location where packages are installed, and hugs/nhc just look in that dir for their packages. Cabal would also look there for the `InstalledPackageInfo` files. So the package db and the libdir are really the same thing. Hugs already looks in `~/lib/hugs/*` for package directories. So for hugs there are two things to do: * make Cabal and hugs agree on where the per-user install path for package should be. Currently cabal-install puts them in `~/.cabal/lib/hugs/*` (or something like that). * get the next release of hugs to include the `InstalledPackageInfo` files for all the packages that it comes with. This will enable cabal to know what packages are installed by reading these files, just as it does with ghc by asking ghc-pkg for the equivalent info. I'm not sure which of Hugs or Cabal should change on the issue of where packages are instelled per-user. I know people would scream if cabal installed things in `~/lib` by default, but perhaps if they're using hugs then they don't care. If we have to get hugs to change anyway to include the `InstalledPackageInfo` files then adding an extra default search path entry for a location under `~/.cabal/` would not be any more work. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/42#comment:3> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #301: No way to reinstall current version of a package
by Hackage 14 Aug '08

14 Aug '08

#301: No way to reinstall current version of a package ----------------------------------+----------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.4.0.1 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.3 Platform: | ----------------------------------+----------------------------------------- cabal-install currently offers no way of reinstalling a version of a package which is already installed. If one has been messing around with libraries behind Cabal's back, this might be useful, if for no other reason than to assuage one's worries regarding link errors. Ideally a flag `--force` or whatever could be given to `cabal upgrade` and `cabal install`, which would make bypass the check for whether the package exists. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/301> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #297: cabal fetch command don't fetch packages those have already been installed
by Hackage 14 Aug '08

14 Aug '08

#297: cabal fetch command don't fetch packages those have already been installed ---------------------------------+------------------------------------------ Reporter: chylli | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ---------------------------------+------------------------------------------ when I saw cabal help: fetch Downloads packages for later installation or study. I think I can fetch any packages to study. But in fact it not. They only download packages those have not installed yet. I think this help info can mislead users. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/297> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

patch applied (cabal-install): Always print the message about nothing to install
by Duncan Coutts 14 Aug '08

14 Aug '08

Thu Aug 14 11:53:04 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Always print the message about nothing to install Not just if the user specified -v or --dry-run. Otherwise it's rather confusing. Also clarify that the reason there is nothing to install is because the latest versions are installed already. Also mention the --reinstall flag: Resolving dependencies... No packages to be installed. All the requested packages are already installed. If you want to reinstall anyway then use the --reinstall flag. M ./Distribution/Client/Install.hs -1 +8 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080814185304-adfee-…

1 0

patch applied (cabal-install): Only look for detailed build reports if we were generating them
by Duncan Coutts 14 Aug '08

14 Aug '08

Thu Aug 14 11:48:37 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Only look for detailed build reports if we were generating them M ./Distribution/Client/Install.hs -3 +4 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080814184837-adfee-…

1 0

patch applied (cabal-install): Add cabal install --reinstall flag
by Duncan Coutts 14 Aug '08

14 Aug '08

Thu Aug 14 11:34:45 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Add cabal install --reinstall flag to force reinstall of package where we have the exact same version already installed. Ordinarily we would say that there is nothing to do as the exact same package version is already installed. There are some cases where you might want to do this, eg to rebuild with different compiler options, or adding/removing components (since we do not track those indifidually yet, eg docs, profiling libs). M ./Distribution/Client/Install.hs -6 +17 M ./Distribution/Client/Setup.hs +8 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080814183445-adfee-…

1 0