Re: [julia-users] Re: Private Forks of Julia Repositories

I did something like this and it worked. I have private repos for github (student) so I used that. I made a private repo, made a branch in my local git repo, pushed that to the new private repo, used this

Re: [julia-users] Re: Private Forks of Julia Repositories

Maybe Playground.jl will fit your use case. It works similarly to Python's virtualenv which allows having multiple versions of the same package to be installed at the same time. https://github.com/Rory-Finnegan/Playground.jl

Re: [julia-users] Re: Private Forks of Julia Repositories

On Fri, 2016-06-03 at 08:45, Chris Rackauckas wrote: > I can keep a private local branch, but then it's only on one computer and I > can't develop/test on any other computer (/hpc). You can have several remotes for one repository. So you can have your private branch on a

Re: [julia-users] Re: Private Forks of Julia Repositories

So if I make a private fork, put it locally in a different folder, add it to the load path in .juliarc.jl, develop privates codes there, setup remotes like in the StackExchange discussion I linked, it seems that would work. However, if I do this there will be two modules in the load path with

Re: [julia-users] Re: Private Forks of Julia Repositories

I can keep a private local branch, but then it's only on one computer and I can't develop/test on any other computer (/hpc). On Thursday, June 2, 2016 at 11:18:09 PM UTC-7, Mauro wrote: > > On Fri, 2016-06-03 at 07:58, Chris Rackauckas > wrote: > > I think I will need

Re: [julia-users] Re: Private Forks of Julia Repositories

I am doing this right now, via Loadpath. Set the loadpath in your `.juliarc.jl` so that an extra folder (where you are working) is also in your loadpath. Control it with Git, (not the julia package mananger). Everything is fine and normal ,it is just another git repo. I have no interest in

Re: [julia-users] Re: Private Forks of Julia Repositories

On Fri, 2016-06-03 at 07:58, Chris Rackauckas wrote: > I think I will need both versions available, since the majority of the work > is public, while the private work will tend to sit around longer (i.e. > waiting to hear back from reviewers). So I'd want to be able to easily