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.
