Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow use of more than one remote repo (hackage). #1605

Closed
schell opened this issue Dec 5, 2013 · 4 comments
Closed

Allow use of more than one remote repo (hackage). #1605

schell opened this issue Dec 5, 2013 · 4 comments

Comments

@schell
Copy link

schell commented Dec 5, 2013

It looks like at some point cabal would support building packages from more than one repo. Is this possible?

@23Skidoo
Copy link
Member

23Skidoo commented Dec 6, 2013

This only requires changing how we parse the --remote-repo option. The globalRemoteRepos fields is already a list:

    globalRemoteRepos       :: [RemoteRepo],     -- ^ Available Hackage servers.

Looking at the code, the possibility of more than one repo is anticipated.

What is the expected use case? Private hackage servers?

@schell
Copy link
Author

schell commented Dec 6, 2013

Yes, a private hackage server.

@dcoutts
Copy link
Contributor

dcoutts commented Dec 18, 2013

As far as I know (i.e. unless it was very recently broken) this just works. You just specify multiple entries in the .cabal/config file (or pass multiple --remote-repo flags on the command line).

e.g.

remote-repo: hackage.haskell.org:http://hackage.haskell.org/
remote-repo: private-collection:http://hackage.local/

Make sure to list the private one second so that it overrides, and so that uploads go there.

@schell
Copy link
Author

schell commented Dec 18, 2013

Thanks @dcoutts! It works. I think before I was passing the --remote-repo arg incorrectly.

@schell schell closed this as completed Dec 18, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants