Depending on your goals and how far along you are, it may be worth forking the project and updating the existing code instead of starting from scratch. Once you get going, make any necessary updates to 0.3 compatibility, etc., then the METADATA URL could be changed to point to your fork. You can always commit to your own fork, but one suggested step is to open an issue on the existing repo to see if the authors respond and are amenable to giving you commit access or transferring the repo (so that issues are preserved). Often authors are quite happy to pass on a dormant project to a new maintainer.
(do we have a Julia database organization this could go to for longer-term conservatorship?) On Tue, Sep 2, 2014 at 10:42 PM, Peter Zion <[email protected]> wrote: > Hi there, > > Apologies first if this is clearly documented somewhere. I'm new to Julia > so I'm still getting used to things like package management. > > I am building new MongoDB bindings for Julia (the existing ones at > pkg.julialang.org appear to be abandoned) and I was hoping I would be > able to make use of Julia's great testing framework. > > In order to do this well I believe that I need to specify a build.jl that > only applies to the tests. The specific case is that the bindings module > only needs to build the Mongo C client library to run, but in order to test > the client you need to build MongoDB itself. Then, the test would run an > instance of the database using a temporary directory etc. and test against > that. > > Is there a way to do specify a build.jl that is only used for testing? Or > do I currently have to had MongoDB itself to the top level deps/build.jl? > > Thanks in advance for any help! > >
