[Hackage] #420: cabal-install upgrade optionally ignore
packages that want a higher base?
Hackage
trac at galois.com
Mon Dec 1 12:28:36 EST 2008
#420: cabal-install upgrade optionally ignore packages that want a higher base?
----------------------------+-----------------------------------------------
Reporter: jimburton | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Cabal library | Version: 1.2.3.0
Severity: normal | Resolution:
Keywords: | Difficulty: normal
Ghcversion: 6.8.3 | Platform:
----------------------------+-----------------------------------------------
Old description:
> If I try to upgrade all packages it fails because syb wants a newer base:
>
> $ cabal upgrade
> Resolving dependencies...
> cabal: cannot configure syb-0.1.0.0. It requires base >=4.0
> There is no available version of base that satisfies >=4.0
>
> I don't want to upgrade GHC (in fact I can't right now) but I presume
> that there are other packages that could upgrade. Rather than run `cabal
> install' on them one by one, what about upgrading everything that is
> upgradeable, i.e. happy with the current base? There is a (misleading)
> analogy to the way apt treats releases -- it won't tell me "Can't upgrade
> because you're using the wrong release", but releases are self-contained
> and upgrades take place within that context...but obviously different
> because there you have different package lists for different releases...
New description:
If I try to upgrade all packages it fails because syb wants a newer base:
{{{
$ cabal upgrade
Resolving dependencies...
cabal: cannot configure syb-0.1.0.0. It requires base >=4.0
There is no available version of base that satisfies >=4.0
}}}
I don't want to upgrade GHC (in fact I can't right now) but I presume that
there are other packages that could upgrade. Rather than run `cabal
install' on them one by one, what about upgrading everything that is
upgradeable, i.e. happy with the current base? There is a (misleading)
analogy to the way apt treats releases -- it won't tell me "Can't upgrade
because you're using the wrong release", but releases are self-contained
and upgrades take place within that context...but obviously different
because there you have different package lists for different releases...
--
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/420#comment:2>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects
More information about the cabal-devel
mailing list