We do something very similar, except use the centralised repository to auto-build packages for each language. Then Python or Go need only get their own package, and don't need to know about the repository at all.
It's really useful having all the defs in one place (auto-building documentation, overview of the systems, interoperability, etc.) On Sun, Nov 24, 2013 at 5:18 AM, Bryan Pham <[email protected]> wrote: > I have a dedicated thrift repository. Projects that need thrift will need > to copy from this centralized repository into its location; generation of > code is done during automated build. I would discourage against git > submodule because you'd have to manage tagging in order to reproduce build > at a certain point in time. > > > On Fri, Nov 22, 2013 at 4:46 PM, Aditya Sarawgi > <[email protected]>wrote: > > > Hey Guys, > > > > Whats the best way to manage thrift files across different projects, git > > submodule ? > > > > > > -- > > Aditya Sarawgi > > > > > > -- > Best, > Bryan Pham > Co-Founder and CTO, CloudTenna Inc. >
