I’m trying to write a package (my first, so apologies for ignorance) using Julia 1.0.1 that depends on the master version of an existing package Pages.jl, but am struggling to enforce this.
My current method is, in REPL
using Pkg Pkg.activate(".") Pkg.add(PackageSpec(name="Pages", rev="master"))
to build the Project.toml and Manifest.toml, the latter now containing
[[Pages]] deps = ["HTTP", "JSON", "PlotlyBase", "Sockets", "Test"] git-tree-sha1 = "a82e00554e2956010b207656d347ff4cae0dee05" repo-rev = "master" repo-url = "https://github.com/EricForgy/Pages.jl.git" uuid = "7c165e09-dada-5b64-9fdc-39b801c58527" version = "0.2.0+"
which seems to capture the requirement in the repo-rev. But when I attempt to load my package by
which is my (poorly written) package, which contains
using Pages#master in the module, and also has the above Manifest.toml in the directory, it reports, under “Resolving package versions…” that it’s got Pages v0.2.0, which is a few crucial revisions prior to the head of master (but also an acceptable version in the manifest.toml above). As a double-check, the functionality of the third-party package is correspondingly not the latest commit.
I’ve almost certainly done something stupid and can’t spot the correct approach in the documentation, so any help would be greatly appreciated in ensuring that I can enforce the dependency on a later commit than is tagged
Thanks - Gavin