Splitting the repos...

[Michael McConville]

Gary Kramlich wrote:
> On Thu, Apr 7, 2016 at 2:18 PM, Michael McConville <mmcco at mykolab.com>
> wrote:
> 
> > Gary Kramlich wrote:
> > > On Thu, Apr 7, 2016 at 1:47 PM, Patrick Cloke <patrick at cloke.us> wrote:
> > > > First off I'll say that splitting this out would like making
> > > > building libpurple for Instantbird easier, so that'd be nice...
> > > >
> > > > It might make development harder, however. This is from my
> > > > experiences developing on Instantbird which has components across 3
> > > > repositories: mozilla-central (UI core, networking, security, etc.
> > > > from Firefox), comm-central (Instantbird and Thunderbird code),
> > > > purplexpcom (libpurple and XPCOM interfaces to libpurple):
> > > >
> > >  Nice I didn't realize there was a purple-xpcom :)  Anyways, how is
> > >  this different than how Pidgin has a ton of external dependencies?
> > >  I'm not trying to justify it, just wondering what makes this
> > >  different.
> >
> > External dependencies are typically just installed with a system package
> > manager. No source or building necessary.
> >
> 
> That's why I have Bamboo setup to export repositories as artifacts/deploys
> that can be used by your system package manager.

I'll have to look into that more. Usually, though, the sort of set up
you describe is far more attractive to the person who designs it than it
is to others. They tend to introduce dark magic and complexity that
people don't want to learn.