(Imported from Trac #53, reported by @syntaxpolice on 2006-01-24)
cabal-get -g install cabal-put
Using config dir: /home/ijones/.cabal-get
cabal-get: Couldn't satisfy dependency: 'cabal-put -any'.
(Imported comment by @dcoutts on 2006-01-24)
(Imported comment by @dcoutts on 2007-09-26)
This is actually a tricky problem. We cannot just go online any old time to update the index. We have to be able to fetch packages and install and re-install them later without having to go online.
So the question is, what are the points when we would have to go online anyway and so it'd be ok to update the index. Are there enough of them, or should we just suggest to update when the index is older than N days.
Can someone come up with a proposal?
(Imported comment by @dcoutts on 2007-12-18)
We currently get:
$ cabal install cabal-upload
Warning: The package list does not exist. Run 'cabal update' to download it.
cabal: Unresolved dependencies: cabal-upload -any
So closing this one as it's fixed. Though we could probably do better, it should be an error straight off rather than a warning followed by another error.