harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Petrenko" <alexey.a.petre...@gmail.com>
Subject Re: [build] managing external dependencies
Date Wed, 16 Jan 2008 12:53:48 GMT
2008/1/16, Alexey Varlamov <alexey.v.varlamov@gmail.com>:
> 2008/1/9, Mark Hindess <mark.hindess@googlemail.com>:
> >
> > On 9 January 2008 at 19:07, "Alexey Varlamov" <alexey.v.varlamov@gmail.com>
wrote:
> > > Folks,
> > >
> > > We did a few iterations refactoring the subject - let's have one more access
> > > ;).
> > > Why? There was a desire to have the following:
> > > 1) More fine-grained control over dependencies to empower modularity;
> > > 2) Unified approach and shared scripts across Harmony modules - VMs,
> > > classlib, jdktools;
> > > 3) Reduce duplication of resources (traffic, space, etc) between
> > > modules within the same workspace;
> > > I'd also add 4) If possible, reuse resources in different workspaces.
> > > This would be quite handy for committing purposes and for
> > > multi-platform development.
> >
> > I like all of the above but would add Tim's suggestion from a few weeks
> > back which I think was something like:
> >
> > 5) Move binary dependencies - like all the icu libs - from the enhanced
> > to the standard tree in svn and download them via http as we do other
> > dependencies during the fetch-depends stage.
>
> +1. Checking out tens of megabytes of unrelated binaries is really annoying!
+1

Mime
View raw message