Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

if cabal get update needs to run, say so #60

Closed
bos opened this Issue May 24, 2012 · 3 comments

Comments

Projects
None yet
2 participants
Contributor

bos commented May 24, 2012

(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'.
the actual problem here is that the user needs to run cabal-get update.

@ghost ghost assigned SyntaxPolice May 24, 2012

Contributor

bos commented May 24, 2012

(Imported comment by @dcoutts on 2006-01-24)

Punt.

Contributor

bos commented May 24, 2012

(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?

Contributor

bos commented May 24, 2012

(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
I misunderstood the request. The original request was just to say when the package list is missing. I interpreted it as knowing to update the package list based on a request to install something that was on the server but not in the current package list, which is rather harder.

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.

@bos bos closed this May 24, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment