Hi Erik,
thanks for the clarification -- being able to download from multiple
repos is indeed useful. Understood about command line utility to upload.
Having thought about this today, we think we might do something along
the same line that integrates with version control. If we don't, I
suspe
Hi Carl,
That's right, upload to multiple repo's doesn't work at all, for
multiple reasons. The advantage of multiple remote-repo's is that
cabal-install pulls from all repo's when installing a package. So you
can have packages depend on both private packages, and packages from
the public hackage,
Hi Erik,
thanks for the suggestion! I tried that, though it appears that the
cabal-install upload command picks up the last repo specified when
running the upload command (Distribution.Client.Upload:65), without an
option to instead use one of the other repos. It's not clear to me what
the ad
Hi Carl,
At Silk, we use a private hackage. You can just enter it in your main
cabal config (~/.cabal/config) as an extra entry:
remote-repo: hackage.haskell.org:http://hackage.haskell.org/packages/archive
remote-repo: :
The only thing that doesn't work well, is the username/password for
'cabal
Hi all,
for packages that aren't for public consumption, we would like to
specify a private Hackage repo location. The simplest way we could think
of to do this was to read a config file in the same format as the user
config (~/.cabal/config) from the current directory and let any flags
set i
