new dependencies

[Dominic Hamon <dh...@twopensource.com>]

Hello

I noticed this week that new dependencies have been added to Mesos: libapr1
and libsubversion. A good practice would be to have changes like this, that
impact the developer community broadly, be more widely communicated.

I don't think either of these libraries are unavailable for our target
platforms, but other dependencies we might add might be. Or the versions
required might be incompatible. Either way, I think it's important that we
are clear when adding a dependency both what is being added, and why.

In that spirit, I'll ask why these libraries were chosen specifically, and
what factors were considered when adding them (as opposed to other
libraries, implementing features ourselves, etc).

Thanks!


-- 
Dominic Hamon | @mrdo | Twitter
*There are no bad ideas; only good ideas that go horribly wrong.*

Re: new dependencies

[Benjamin Mahler <be...@gmail.com>]

Hey Tim,

Could you file newbie tickets for these two pain points?

(1) No OS X getting started instructions on the website.
(2) Have ./configure be smarter for OS X users using homebrew, seems like a
huge pain to be running:
../configure --with-apr=/usr/local/Cellar/apr/1.5.1
--with-svn=/usr/local/Cellar/subversion/1.8.10_1

Thanks!

On Wed, Oct 29, 2014 at 2:02 PM, Timothy Chen <tn...@gmail.com> wrote:

> Hi Dominic,
>
> Thanks for the email, sorry I was thinking about writing an email to
> the list about the new dependencies but didn't get to it.
>
> I'll let BenH talk about why he used libsvn (libapr is a dependency
> for libsvn) for implementing diffs.
>
> I've updated the getting-started.md doc as part of the patch to look
> for libsvn and libapr headers, about instructions for CentOS and
> Ubuntu.
>
> For Mac OSX users, you can find subversion in the homebrew/versions
> tap and apr in the homebrew/apache tap. The only caveat is to either
> symlink the include header folders from /usr/local/Cellar folders to
> usr/include, or specify the directories with --with-apr and --with-svn
> flags to configure.
>
> Thanks!
>
> Tim
>
> On Wed, Oct 29, 2014 at 1:29 PM, Dominic Hamon <dh...@twopensource.com>
> wrote:
> > Hello
> >
> > I noticed this week that new dependencies have been added to Mesos:
> libapr1
> > and libsubversion. A good practice would be to have changes like this,
> that
> > impact the developer community broadly, be more widely communicated.
> >
> > I don't think either of these libraries are unavailable for our target
> > platforms, but other dependencies we might add might be. Or the versions
> > required might be incompatible. Either way, I think it's important that
> we
> > are clear when adding a dependency both what is being added, and why.
> >
> > In that spirit, I'll ask why these libraries were chosen specifically,
> and
> > what factors were considered when adding them (as opposed to other
> > libraries, implementing features ourselves, etc).
> >
> > Thanks!
> >
> >
> > --
> > Dominic Hamon | @mrdo | Twitter
> > *There are no bad ideas; only good ideas that go horribly wrong.*
>

Re: new dependencies

[Timothy Chen <tn...@gmail.com>]

Hi Dominic,

Thanks for the email, sorry I was thinking about writing an email to
the list about the new dependencies but didn't get to it.

I'll let BenH talk about why he used libsvn (libapr is a dependency
for libsvn) for implementing diffs.

I've updated the getting-started.md doc as part of the patch to look
for libsvn and libapr headers, about instructions for CentOS and
Ubuntu.

For Mac OSX users, you can find subversion in the homebrew/versions
tap and apr in the homebrew/apache tap. The only caveat is to either
symlink the include header folders from /usr/local/Cellar folders to
usr/include, or specify the directories with --with-apr and --with-svn
flags to configure.

Thanks!

Tim

On Wed, Oct 29, 2014 at 1:29 PM, Dominic Hamon <dh...@twopensource.com> wrote:
> Hello
>
> I noticed this week that new dependencies have been added to Mesos: libapr1
> and libsubversion. A good practice would be to have changes like this, that
> impact the developer community broadly, be more widely communicated.
>
> I don't think either of these libraries are unavailable for our target
> platforms, but other dependencies we might add might be. Or the versions
> required might be incompatible. Either way, I think it's important that we
> are clear when adding a dependency both what is being added, and why.
>
> In that spirit, I'll ask why these libraries were chosen specifically, and
> what factors were considered when adding them (as opposed to other
> libraries, implementing features ourselves, etc).
>
> Thanks!
>
>
> --
> Dominic Hamon | @mrdo | Twitter
> *There are no bad ideas; only good ideas that go horribly wrong.*