Re: [Hackage] #140: Cabal doesn't allow doc/html/ to be overridden

> closed Comment: Fixed. The Windows doc path default could still probably do with tweaking, especially for libraries. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/140> Hackage <http://example.com/> My example project

[Hackage] #148: Cabal should be able to produce DLLs in Windows

. Cabal should support this use, and also support specifying DEF file for exports and building an import library. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/148> Hackage <http://example.com/> My example project___ cabal-d

[Hackage] #149: Support for building and linking resource files in Windows

and files and link them to at least executable (.exe and .dll). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/149> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www

[Hackage] #150: haddock docs are installed insensibly in Windows

each other via relative paths, but ghc installation isn't installed in similar fashion. And then all packages must also be installed into same prefix. (ie user-only vs admin installs) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/150> Hackage <http://examp

[Hackage] #151: license file is not installed

org/trac/hackage/ticket/151> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #22: a bunch of windows problems

nux --+- Changes (by duncan): * component: cabal-get => Cabal -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/22> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http

Re: [Hackage] #35: cabal-get needs a way to list available packages

-+-- Changes (by duncan): * ghcversion: => 6.2.1 * component: cabal-get => cabal-install * platform: => Linux Comment: I think cabal-install does this now. Some cabal-install person should double check and close this. -- Ticket URL: <http://hackage.haskell.org/trac/ha

Re: [Hackage] #52: cabal-get should pick a default compiler instead of giving an error the first time you run it

+--- Changes (by duncan): * component: cabal-get => cabal-install -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/52> Hackage <http://example.com/> My example project___ cabal-devel mai

Re: [Hackage] #53: if cabal get update needs to run, say so

duncan): * ghcversion: => 6.2.1 * component: cabal-get => cabal-install * platform: => Linux -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/53> Hackage <http://example.com/> My example project___ cabal-dev

Re: [Hackage] #54: if a package is already newest version, avoid downloading and installing it

+--- Changes (by duncan): * ghcversion: => 6.2.1 * component: cabal-get => cabal-install * platform: => Linux -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/54> Hackage <http://exampl

Re: [Hackage] #55: should cabal-upload be a thin wrapper on cabal-install?

---+ Changes (by duncan): * component: cabal-get => cabal-upload * summary: should cabal-put be a thin wrapper on cabal-install => should cabal-upload be a thin wrapper on cabal- install? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/55> H

Re: [Hackage] #60: make cabal-get-bootstrap release

): * component: cabal-get => cabal-install Comment: This is terribly out of date. But we should have a cabal-install release. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/60> Hackage <http://example.com/> My example project__

Re: [Hackage] #62: implement "new age" cabal-get/put in order to make it possible to distribute cabal-get w/ cabal

rm: Linux +--- Changes (by duncan): * component: cabal-get => cabal-install -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/62> Hackage <http://example.com/> My example project___

Re: [Hackage] #64: enhance cabal-get to perform local installation tasks

): * component: cabal-get => cabal-install -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/64> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/m

Re: [Hackage] #71: cabal-get should install packages locally

): * component: cabal-get => cabal-install -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/71> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman

Re: [Hackage] #87: robustify & release cabal-get

-get => cabal-install -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/87> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #7: add --ghc-args and such to configure

e flags apply for all programs that cabal knows about (which is also extensible via hooks). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/7> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@h

Re: [Hackage] #5: convert non-preprocessor calls to use Distribution.Program

): * resolution: => fixed * status: assigned => closed Comment: Done. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/5> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-deve

Re: [Hackage] #31: generate CabalInfo.hs from PacakageDescription and LocalBuildInfo

--+- Changes (by duncan): * resolution: => fixed * status: new => closed Comment: We do generate the Paths_.hs module. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/31> Hackage <http://example.com/> My example project_

Re: [Hackage] #63: implement thin tool for installing packages w/ correct version of cabal ("cabal-setup")

rm: Linux --+- Changes (by duncan): * component: Cabal => cabal-setup -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/63> Hackage <http://example.com/> My example project___ cabal-devel mailing list cab

Re: [Hackage] #55: should cabal-upload be a thin wrapper on cabal-install?

---+ Comment (by [EMAIL PROTECTED]): I don't see the connection. cabal-upload is currently a small program that wraps a package in a request to the upload CGI script, while cabal-install fetches the files it needs via HTTP. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/55> Ha

Re: [Hackage] #148: Cabal should be able to produce DLLs in Windows

Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/148> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #151: license file is not installed

nux --+- Changes (by duncan): * difficulty: normal => very easy (<1 hour) * milestone: => Cabal-1.2 * version: 1.1.6 => HEAD -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/151> Hackage <http://

Re: [Hackage] #7: add --ghc-args and such to configure

tion elsewhere). The latter takes only one option, so multiple options must each be wrapped individually. That can be a bit more cumbersome, but it avoids issues with embedded spaces. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/7> Hackage <http://e

Re: [Hackage] #150: haddock docs are installed insensibly in Windows

Making the docs relocatable is hard. Fixing the default location should be done for cabal 1.2, the other will have to be deferred. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/150> Hackage <http://example.com/> My example project_

Re: [Hackage] #149: Support for building and linking resource files in Windows

(by duncan): * milestone: => Cabal-1.4 * platform: Linux => Windows * version: 1.1.6 => HEAD -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/149> Hackage <http://example.com/> My example project___ cabal-dev

Re: [Hackage] #38: craft workaround for gentoo which allows them to generate package.conf file but not register

--+- Changes (by [EMAIL PROTECTED]): * resolution: fixed => * status: closed => reopened Comment: The interface change is not documented in the User's Guide. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/38> Hackage <http://exam

[Hackage] #152: sdist doesn't include install-includes

ed in install-includes won't end up in the tarball created by sdist. As c-sources get included and install-includes are not to be provided by the system, I think it's the right thing to include them in sdist. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/

Re: [Hackage] #132: Add "tools" field (like "extensions")

ram, so it's not for the general notion of requiring C style pre-processing. So I think CPP is an extension, and ghc, cpp and cpphs are possible programs that cabal may choose to implement the CPP language extension. So in fact Cabal does not even know about the "cpp" program as it use

Re: [Hackage] #152: sdist doesn't include install-includes

Linux --+- Changes (by duncan): * milestone: => Cabal-1.2 * priority: normal => high * version: 1.1.6 => HEAD -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/152> Hackage <http://example.com/> My example project_

Re: [Hackage] #123: option to configure haddock documentation install directory

ckage.haskell.org/trac/hackage/ticket/123> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #38: craft workaround for gentoo which allows them to generate package.conf file but not register

--+- Changes (by duncan): * resolution: => fixed * status: reopened => closed -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/38> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal

Re: [Hackage] #38: craft workaround for gentoo which allows them to generate package.conf file but not register

--+- Comment (by duncan): Now documented. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/38> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www

Re: [Hackage] #132: Add "tools" field (like "extensions")

| Platform: Linux --+- Changes (by duncan): * cc: => [EMAIL PROTECTED] Comment: Now documented too. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/132> Hackage <http://example.com/> My example project___ cabal-deve

Re: [Hackage] #109: undocumented options

duncan): --enable-haddock-use-packages and --disable-haddock-use-packages are now not just no longer used but actually removed from the configure --help option list! -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/109> Hackage <http://example.com/>

Re: [Hackage] #116: Odd paths on Windows

on Windows. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/116> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #3: document or remove --enable-library-for-ghci / --disable-library-for-ghc flags

+--- Comment (by duncan): They are now documented. It would be possible with ghc-6.8 to make this decision automatically based on the output of ghc --info which would be preferable. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/3> Hackage <http://example.com/>

Re: [Hackage] #109: undocumented options

duncan): * resolution: => fixed * status: new => closed Comment: Done. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/109> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-deve

Re: [Hackage] #3: document or remove --enable-library-for-ghci / --disable-library-for-ghc flags

+--- Changes (by duncan): * resolution: => fixed * status: new => closed -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/3> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-deve

Re: [Hackage] #118: Cabal eats leading '.'s from .cabal file

http://hackage.haskell.org/trac/hackage/ticket/118> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #97: Should not create empty directories in setup install/copy

: => fixed * status: new => closed Comment: The include dir will now only be made and noted in the package registration info if we actually install some include files. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/97> Hackage <http://example.c

Re: [Hackage] #41: convert 'tar' call in SrcDist.hs to use Distribution.Program

ed * status: new => closed Comment: Done. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/41> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #152: sdist doesn't include install-includes

Linux --+- Changes (by duncan): * resolution: => fixed * status: new => closed Comment: Fixed. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/152> Hackage <http://example.com/> My example project

Re: [Hackage] #151: license file is not installed

nux --+- Changes (by duncan): * resolution: => fixed * status: new => closed Comment: Done. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/151> Hackage <http://example.com/> My example project__

Re: [Hackage] #118: Cabal eats leading '.'s from .cabal file

th, I haven't tested though. The problem described in the original report should be fixed, though it's sad we do not seem to have regression tests for this one. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/118> Hackage <http://example.com/> My example proje

Re: [Hackage] #118: Cabal eats leading '.'s from .cabal file

(by duncan): * resolution: => fixed * status: new => closed Comment: Now fixed by not using normalize in a few places. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/118> Hackage <http://example.com/> My example project___

Re: [Hackage] #116: Odd paths on Windows

fix on Windows now includes the trailing Haskell, so if you override prefix then you don't get any Haskell sub dir. Also, the docs are now installed relative to prefix. And the user guide has been updated. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/116> Hackage &l

Re: [Hackage] #150: haddock docs are not relocatable in Windows

omment: The default location has been improved. It doesn't contain the compiler however. But you can override that with --docdir=... Changing summary, priority & difficulty to reflect the remaining part of the problem. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/150&

Re: [Hackage] #7: add --ghc-args and such to configure

course is to use {{{ ./setup configure --foo-arg=--bar="some path with spaces" }}} again, assuming your shell parses {{{--foo-arg=--bar="some path with spaces"}}} into a single argument {{{--foo-arg=--bar=some path with spaces}}}. Oh the joys of

Re: [Hackage] #132: Add "tools" field (like "extensions")

| Platform: Linux --+- Changes (by duncan): * resolution: => fixed * status: new => closed -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/132> Hackage <http://example.com/> My example project___

Re: [Hackage] #27: Document configurations syntax

asy (<1 hour) * milestone: Cabal-1.4 => Cabal-1.2 * summary: Configurations => Document configurations syntax Comment: Configurations are now implemented, the latest syntax needs to be documented in the user guide. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/27>

Re: [Hackage] #141: Cabal throws an ugly "irrefutable pattern match failed" error when confronted to an empty .cabal descriptor

://hackage.haskell.org/trac/hackage/ticket/141> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

[Hackage] #153: Cabal makes empty data directories

ory... (No idea which) }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/153> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #153: Cabal makes empty data directories

omment: Applied, thanks. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/153> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #104: "setup install" should configure and build if necessary

tform: Linux -+-- Changes (by duncan): * milestone: Cabal-1.2 => Comment: I'm not sure if cabal-install reduces the desire for this feature. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/104> Hackage <http://example.com/> My example project

Re: [Hackage] #110: cabal should detect when a new version of a library is installed

+--- Changes (by duncan): * milestone: Cabal-1.2 => Comment: Currently recompilation checking is deferred to ghc and it does not check packages at the moment. See http://hackage.haskell.org/trac/ghc/ticket/1372 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/

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

hci support is one of these things. So we could support this feature in ghc-6.8 and later. If we do this, should we drop the existing --disable-library-for-ghci flag? We could keep it if we tried the {{{ghc -e "return ()"}}} suggestion. -- Ticket URL: <http://hackage.haskell

Re: [Hackage] #65: reorganize layered tool system (cabal-get, cabal-install, cabal-setup, etc)

s packages and deps from hackage. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/65> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

[Hackage] #154: Cabal doesn't clean "_stub" files

,h} files in Cabal-1.2.0. It does in 1.1.6.2. The -stubdir flag might be useful here (introduced in ghc-6.6) for having them created in the dist/build directory. (In both 1.2.0 and 1.1.6.2, they're created next to the source .hs files.) Related: [542]. -- Ticket URL: <http://hacka

[Hackage] #155: show . readPackageDescription /= id

art K -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/155> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #147: Replace Extension type with (newtyped?) String

): * milestone: => Cabal-1.4 * type: defect => enhancement -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/147> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-deve

Re: [Hackage] #134: Clean up hooks

(by duncan): * difficulty: normal => very hard (<1 week) * milestone: => Cabal-1.4 * type: defect => task -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/134> Hackage <http://example.com/> My example project_

Re: [Hackage] #120: misleading error message from cabal when versions differ

ell.org/trac/hackage/ticket/120> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #98: cabal assumes -x option for linking

nix +--- Changes (by duncan): * difficulty: normal => easy (<4 hours) * milestone: => Cabal-1.4 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/98> Hackage <http://example.com/> My example project___

Re: [Hackage] #133: sdist and clean should never be given Maybe LocalBuildInfo

ges (by duncan): * difficulty: normal => hard (< 1 day) * milestone: => Cabal-1.4 * type: defect => task Comment: See also bug #134 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/133> Hackage <http://

Re: [Hackage] #103: feature request: preprocess files with ghc before haddock?

se I think it's not something we can fix in Cabal. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/103> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell

Re: [Hackage] #125: running Haddock with different options not possible

-+-- Comment (by duncan): There is now a configure --haddock-options flag that passes extra flags to haddock. Does this help at all? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example

Re: [Hackage] #144: confusing blank line before `executable`

---+ Changes (by duncan): * resolution: => fixed * status: new => closed Comment: Fixed with the new cabal file parser. The blank line is no longer required and so missing it out is not a problem. -- Ticket URL: <http://hackage.haskell.org/tra

Re: [Hackage] #154: Cabal doesn't clean "_stub" files

d * status: new => closed Comment: Fixed, for ghc-6.6 and later at least by using -stubdir. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/154> Hackage <http://example.com/> My example project___ cabal-devel mailing

Re: [Hackage] #125: running Haddock with different options not possible

ttp://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #125: running Haddock with different options not possible

-exports}}}. Cabal has to run Haddock on all modules of the package, not just the modules which are exposed. Could such a feature be implemented as well? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example.com/>

Re: [Hackage] #125: running Haddock with different options not possible

-+-- Comment (by duncan): So can we open a new bug for that feature request and close this bug now? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example.com/>

[Hackage] #156: setup haddock: option to expose all modules

option to turn this off, so that all modules appear in the documentation? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/156> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@hask

Re: [Hackage] #125: running Haddock with different options not possible

-+-- Changes (by [EMAIL PROTECTED]): * resolution: => fixed * status: new => closed Comment: new request opened as #156 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example.c

Re: [Hackage] #156: setup haddock: option to expose all modules

--+- Changes (by [EMAIL PROTECTED]): * cc: => [EMAIL PROTECTED] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/156> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@h

Re: [Hackage] #104: "setup install" should configure and build if necessary

PROTECTED]): * difficulty: easy (<4 hours) => normal * type: task => enhancement -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/104> Hackage <http://example.com/> My example project___ cabal-devel mailing li

[Hackage] #157: Haddock command fails when dependent documentation is not installed

bal hacker to have a go at. It should just require modifying makeReadInterface in the Distribution.Simple.Haddock module. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/157> Hackage <http://example.com/> My example project__

Re: [Hackage] #14: allow preprocessing for Main modules

}}} and it'll look for any suitable file that can be pre-processed into {{{Main.hs}}}, like {{{Main.hsc}}} for example. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/14> Hackage <http://example.com/> My example project

Re: [Hackage] #157: Haddock command fails when dependent documentation is not installed

nux -+-- Changes (by duncan): * resolution: => fixed * status: new => closed -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/157> Hackage <http://example.com/> My example project___ cabal-devel mailing list ca

Re: [Hackage] #14: allow preprocessing for Main modules

tus: assigned => closed -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/14> Hackage <http://example.com/> My example project___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

[Hackage] #158: if os(windows) does not work

hat this works: {{{ if os(windows) blah }}} At a bare minimum we should add an alias system, such that we can specify {{{windows}}} and {{{solaris}}} rather than the cryptic {{{mingw32}}} and {{{solaris2}}}. I suggest that comparisons also be case insensetive. -- Ticket URL: <http://h

Re: [Hackage] #158: if os(windows) does not work

can): * status: new => closed * resolution: => fixed Comment: Fixed in Cabal HEAD. Should get moved to the 1.2 branch soon. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/158#comment:1> Hackage <http://example.com/> My example project

Re: [Hackage] #63: implement thin tool for installing packages w/ correct version of cabal ("cabal-setup")

tp://hackage.haskell.org/trac/hackage/ticket/63#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #155: show . readPackageDescription /= id

property: {{{ prop_idempParsePrint x = (r . s . r) x == r x where r = readPackageDescription; s = showPackageDescription }}} I agree that this would be nice to have, though. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/155#comment:1> Hackage <http://haskell.org/cabal/> Hackag

Re: [Hackage] #60: make cabal-get-bootstrap release

out. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/60#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #62: implement "new age" cabal-get/put in order to make it possible to distribute cabal-get w/ cabal

rm: Linux +--- Changes (by duncan): * status: new => closed * resolution: => fixed Comment: Hackage is working well. cabal-install will be released some time after ghc-6.8.1. It will not be included in the Cabal package since it has more depen

Re: [Hackage] #27: Document configurations syntax

ket URL: <http://hackage.haskell.org/trac/hackage/ticket/27#comment:8> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: [Hackage] #53: if cabal get update needs to run, say so

duncan): * milestone: Cabal-1.2 => Cabal-1.4 Comment: Punt. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/53#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects___ cabal-devel mailing l

Re: [Hackage] #155: show . readPackageDescription /= id

+--- Comment (by duncan): This works now I think. Can someone check it and close this bug please. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/155#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal

Re: [Hackage] #160: PatternSignatures missing in Extensions

nux -+-- Comment (by guest): I'ld like to add that the error message for a wrong entry under extensions is quite poor: {{{ Parse of field 'extensions' failed: }}} [EMAIL PROTECTED] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/160#comment:1> Hac

[Hackage] #164: bad error message when using configuration flags that were not defined

ted by {{{Distribution.Configuration.simplifyCondTree}}} but the error should probably be checked for much earlier. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/164> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

Re: [Hackage] #98: cabal assumes -x option for linking

ticket needs a desperate fix for the ghc-6.8.1 release! Furthermore the generated file libraries/base/GNUMakefile contained "`xargs -s 3`" which is too big for Solaris (the maximal value is 2048) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/98#comment:2>

Re: [Hackage] #98: cabal assumes -x option for linking

xtwarn] warn if there are relocations against text [-z verbose]generate warnings for suspicious processings gmake[2]: *** [dist/build/HSbase-3.0.o] Error 1 }}} I could continue with a gnu linker only after cleaning up completely. -- Ticket URL: <http://hackage.haskell.org/t

Re: [Hackage] #98: cabal assumes -x option for linking

urn is based on the Solaris linker. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/98#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@h

Re: [Hackage] #98: cabal assumes -x option for linking

cal syms in .symtab to a minimum }}}. Maybe it could even be omitted. There actually is a FIXMe in Distrubution/Simple/GHC.hs line 348. Could you try removing that line, rebuild Cabal and try again? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/98#comment:5> Hack

Re: [Hackage] #98: cabal assumes -x option for linking

orm: Other Unix ---+ Comment (by guest): Omitting this line works under Solaris. Maybe this explains why my binaries are about 20% bigger. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/98#com

Re: [Hackage] #98: cabal assumes -x option for linking

orm: Other Unix ---+ Comment (by guest): No, it did no work yet. It seems I have to edit `libraries/Cabal/Distribution/Simple/GHC/Makefile.in`, too! -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/98#c

Re: [Hackage] #98: cabal assumes -x option for linking

ue for a (new or further) LDFLAGS variable that is then used in conjunction with LD (instead of -x). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/98#comment:11> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects__

Re: [Hackage] #98: cabal assumes -x option for linking

ate flags are. As it happens because of the Makefile stuff we'll have to fix it in two places in Cabal, once for the ordinary Cabal build stuff and once for where Cabal generates the Makefile. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/98#comment:10> Hackage &

Re: [Hackage] #98: cabal assumes -x option for linking

ket URL: <http://hackage.haskell.org/trac/hackage/ticket/98#comment:9> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

  1   2   3   4   5   6   7   8   9   10   >