>
> I would hope that this is a release blocker issue, given that private
> package repos have been supported forever.
>
So right now there seems no way to use them on 0.5 from Windows...
https:// should be supported, although I haven't tried it on Windows. See
[1,2] for configuration details and instructions to avoid password prompts.
Regarding ssh, see [3]:
building against libssh2 is explicitly disabled by our Makefile.
(this line [2])
Switching ssh on for windows would require Makefile rules to build and
package libssh2 along with libgit2 and the rest of the libraries. Note that
libssh2 can use native windows crypto functionality ("WinCNG" backend), so
it should not impose any further requirements.
[1]
https://help.github.com/articles/which-remote-url-should-i-use/#cloning-with-https-urls-recommended
[2]
http://stackoverflow.com/questions/13800289/configure-git-clients-like-github-for-windows-to-not-ask-for-authentication/18607931#18607931
[3] https://groups.google.com/d/msg/julia-users/GEwX49wwmdo/CihXC62yCAAJ
[4]
https://github.com/JuliaLang/julia/blob/c2042326cc5d68db01c0b2e0d12a15f48b03563a/deps/Makefile#L2094
On Fri, Apr 22, 2016 at 8:30 PM, David Anthoff <[email protected]> wrote:
> Yes, I would hope that this is a release blocker issue, given that private
> package repos have been supported forever. I also have a very large number
> of private repos.
>
> So right now there seems no way to use them on 0.5 from Windows...
>
> I also would prefer to use SSH keys for authentication. If it does have to
> be https, I guess it would be ok if things are integrated with the git
> credential storage infrastructure. What would really be sort of a disaster
> is if I was asked for a username and password every time I do an
> Pkg.update() or something like that...
>
> > -----Original Message-----
> > From: [email protected] [mailto:julia-
> > [email protected]] On Behalf Of Eric Forgy
> > Sent: Friday, April 22, 2016 4:58 PM
> > To: julia-users <[email protected]>
> > Subject: RE: [julia-users] Cloning private package with 0.5
> >
> > I have the same problem (on Windows) and really hoping this gets fixed
> > before 0.5 is released. I have a ton of private repos.
> >
> > I'd prefer a solution that lets me keep my remotes at
> > [email protected]:EricForgy/MyPrivateRepo.jl. It would be more than a
> little
> > annoying if I have to change every one to https. Hopefully, Pkg can do
> some
> > magic and make the changes for me if needed.
>
