Hi folks,
On Mon, Dec 14, 2009 at 8:15 AM, Charles Oliver Nutter
<[email protected]> wrote:
> Sergio (serabe) suggested adding ByteList as a submodule in Git. It
> seems like a good idea; we could keep them separate repositories, but
> still have the source available for debugging. I'm no expert on
> submodules, though, so I'm not sure the right way to structure it.
Yeah, the ByteList is pretty hard to use without sources, so having
the source available
might be a plus.
On the other hand, the submodules thing is pretty confusing, and it
seems that, for example, rbx folks moved completely away from them for
some reason. Would be good to check with them and get the reasons why.
Well, in our case, it seems, that these submodules are more like extra
bonus, and we're not going to use the sources from submodules in our
build process, we would just have sources available to look at, right?
> I've attached a format-patch that adds four submodules for bytelist,
> joni, jcodings, and jruby-openssl, the primary set of libraries that
> we maintain separately and which are generally necessary for most
> users. Let me know what you all think...
Looking at the patch I see that the sources are not attached into our
build process, they just stay there, in modules directory, being there
just for the reference. That looks good.
How about other external projects that I often find a need to look at?
jnr-posix? Ah, drat, jnr-posix is under mercurial.... :)
JRuby launcher for Windows might as well go as submodule...
Thanks,
--Vladimir
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
