Let’s say I have a repository
foo_app consisting of an application (written in another language) and also the Julia bindings for that application. In my mind, this application is not, itself, a Julia package, so it makes sense to call the repository
foo_app rather than
Foo.jl. I was wondering if you all had any recommendations for publishing the Julia bindings in such an instance.
Option 1 would be to put the Julia bindings in a new repo,
Foo.jl and have them depend on
foo_app as an external dependency (or a git submodule). That makes it easy to have a self-contained package of Julia bindings, but also makes my life a bit more complex since I have to manage two repos and keep them in sync.
Option 2 would be to try to format the
foo_app repo so that it can also function as a Julia package. That would mean, at least, giving it a
src folder containing
Foo.jl and a
REQUIRE file at the top level. This means only managing one repo, but it feels like kind of a mess, since it makes it hard to cleanly separate the Julia and non-Julia components.
Is there another option? I recall something from JuliaCon about Pkg3 allowing packages to live in subfolders, so perhaps I could have
Foo.jl as a subfolder of