Re: Dependency directories?

[Henri Yandell <ba...@apache.org>]

I'm not sure for C/C++.

For the languages that have artifact repositories (Java, Python, Perl etc),
the norm is to use those systems.

It does feel weird to have an Apache source project with a large lump of
its code appearing to be the same product but not part of the project.

The approaches that naively jump out to me are:

1) As it currently is, linking MXNet to the other git repositories.
2) User installs them themselves and MXNet uses configure/make to build.
3) Copy the source over into the MXNet project.
4) Create new repositories at Apache for each of them (and then possibly
still just link them in).

Jim (or anyone else) - any advice you could offer on how C/C++ dependencies
are handled at Apache projects?


Hen

On Tue, Aug 29, 2017 at 10:55 PM, Chris Olivier <cj...@gmail.com>
wrote:

> I've been curious about the same thing. How do other Apache projects handle
> this sort of thing?
>
> What's are the pros and cons?
>
>
> On Tue, Aug 29, 2017 at 9:57 PM Henri Yandell <ba...@apache.org> wrote:
>
> > What's the plan for the source that isn't included in the mxnet repo?
> >
> >  cub/
> >  dlpack/
> >  dmlc-core/
> >  mshadow/
> >  nnvm/
> >  ps-lite/
> >
> > Is the plan to keep those as separate DMLC packages, or to consider them
> > MXNet specific?
> >
> > Thanks,
> >
> > Hen
> >
>