As I expected I'm having issues because I haven't kept up, for example, I can't update my version from 0.0.0 to 0.0.1 after a contributor merged changes, and Pkg.publish always returns:
*ERROR: METADATA is behind origin/metadata-v2 – run `Pkg.update()` before publishing* * in publish at pkg/entry.jl:306* * in anonymous at pkg/dir.jl:25* * in cd at file.jl:22* * in cd at pkg/dir.jl:25* * in publish at pkg.jl:57* Even though I've already done Pkg.update(). I'd rather not have to delete my repo and start again from Pkg.generate() again. Best, Ben. On Friday, January 17, 2014 10:06:12 PM UTC, Ben Ward wrote: > > Hi, > > I've been working on an R project as part of a PhD project for a long time > and so have only recently returned to take a look at the Phylogenetics.jl > package I started to create a while ago. Reading the documentation on > packages I see what look to me like changes, like publishing checking out > branches and such all from within Julia, this is somewhat different to the > set up I have: I had a repository on github and on my macbook in a folder > on my desktop, and this was the actual repo and when I used julia and > tested the package this folder was ln -s into the .julia folder, and my > METADATA was similarly linked into .julia. I then made commits to these > with the github gui for osx and just pushed changes and switched branches > as I needed. Is this kind of arrangement still acceptable or is there a > better way of updating your package and working with updating METADATA now? > Just think maybe I need to change my setup to avoid problems. > > Thanks, > Ben. >
