-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/6/10 23:09 , wren ng thornton wrote:
On 11/6/10 6:20 AM, Reiner Pope wrote:
I was aware of this condition, but I'm not precisely sure it addresses
my requirements. When you run cabal install some-package, cabal
reads all version constraints
On Sun, Nov 7, 2010 at 3:58 PM, wren ng thornton w...@freegeek.org wrote:
On 11/7/10 11:54 AM, Henning Thielemann wrote:
Awful - I would not like to complicate my Cabal files this way. This is
like copying the Build-Depends enumeration to all depending packages.
Oh, I agree :)
I wonder if
wren ng thornton schrieb:
On 11/6/10 6:20 AM, Reiner Pope wrote:
I was aware of this condition, but I'm not precisely sure it addresses
my requirements. When you run cabal install some-package, cabal
reads all version constraints listed in the build-depends field, and
chooses which versions
On 11/7/10 11:54 AM, Henning Thielemann wrote:
Awful - I would not like to complicate my Cabal files this way. This is
like copying the Build-Depends enumeration to all depending packages.
Oh, I agree :)
I wonder if you can include ghc in the build-tools: field and whether
cabal-install
Ah, I hadn't thought of that. But doesn't the version of GHC change
much more often than the version of base does?
Reiner
On 6 November 2010 03:49, Ozgur Akgun ozgurak...@gmail.com wrote:
AFAIK, the way to do this is putting constraints on the base package.
On 5 November 2010 14:59, Reiner
On 6 November 2010 17:52, Reiner Pope reiner.p...@gmail.com wrote:
Ah, I hadn't thought of that. But doesn't the version of GHC change
much more often than the version of base does?
Each major version of GHC has a different (major) version of base.
I think you can also say stuff like ghc =
On 11/6/10 3:13 AM, Ivan Lazar Miljenovic wrote:
On 6 November 2010 17:52, Reiner Popereiner.p...@gmail.com wrote:
Ah, I hadn't thought of that. But doesn't the version of GHC change
much more often than the version of base does?
Each major version of GHC has a different (major) version of
I was aware of this condition, but I'm not precisely sure it addresses
my requirements. When you run cabal install some-package, cabal
reads all version constraints listed in the build-depends field, and
chooses which versions of which packages to download from Hackage in
order to satisfy these
On 11/6/10 6:20 AM, Reiner Pope wrote:
I was aware of this condition, but I'm not precisely sure it addresses
my requirements. When you run cabal install some-package, cabal
reads all version constraints listed in the build-depends field, and
chooses which versions of which packages to download
Hi,
I have a library, hmatrix-static, on Hackage. Version 0.3 (the current
version) compiles with ghc-6.12.
Let's say I want to upgrade my library using new features in ghc-7.0,
and then release these upgrades as version 0.4. Is there any way to
state in my cabal file that this new version will
AFAIK, the way to do this is putting constraints on the base package.
On 5 November 2010 14:59, Reiner Pope reiner.p...@gmail.com wrote:
Hi,
I have a library, hmatrix-static, on Hackage. Version 0.3 (the current
version) compiles with ghc-6.12.
Let's say I want to upgrade my library using
11 matches
Mail list logo
