I think the core insight is that a package has two components:
(1) A module called GalaxyBlue
(2) A file, in a searchable package directory like Pkg.dir(), that’s called
something like GalaxyBlue/src/GalaxyBlue.jl.
For 2, that means you have a directory (usually a repo) containing the package
code, a subdirectory called src and then a file called PACKAGENAME.jl, which
will be automatically loaded. That file should contain the definition of your
module.
I’m not sure, but I suspect that Pkg.clone with a second argument isn’t
changing the content of that file.
— John
On Feb 25, 2014, at 7:01 AM, ben <benjamin.conna...@gmail.com> wrote:
> Hi,
>
> Is it possible for two different packages to contain identically named
> modules?
>
> For instance, if I fork a package Galaxy.jl, and then
>
> > Pkg.clone("github/fork/url/Galaxy.jl.git", GalaxyBlue)
>
> (So that both the original package and my forked version live side-by-side in
> my .julia repository.) How do I then use GalaxyBlue? "using GalaxyBlue" and
> "require("GalaxyBlue")" both give me "ERROR: GalaxyBlue" not found.
>
> I guess I am generally confused about package names v. module names and I was
> not able to find documentation on this.
>
> Thanks!
>
> Ben
