FWIW, I've created a sample project using olso as a submodule: https://github.com/novel/oslo-helloworld
I spotted some minor difficulties: 1. As olso directory layout is not designed to be used as a submodule, a symlink has to be created to place code to the proper location 2. sys.path hack has to be applied for proper imports On Thu, Aug 8, 2013 at 2:39 PM, Mark McLoughlin <mar...@redhat.com> wrote: > What do you mean by "dangerous code merging" in the subject? The body of > your mail doesn't make any reference to whatever "danger" you're seeing. > > On Thu, 2013-08-08 at 14:16 +0400, Boris Pavlovic wrote: > > Hi All, > > > > Could somebody answer me, why we are merging oslo code in other projects > > and don't use > > git submodules (http://git-scm.com/book/en/Git-Tools-Submodules) > > The idea of using submodules has come a few times. I don't have a > fundamental objection to it, except any time I've seen submodules used > in a project they've been extremely painful for everyone involved. > > I'd be happy to look at a demo of a submodule based system for projects > to use code from oslo-incubator. > > Mark. > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev