On Tue, Jan 19, 2016 at 9:08 PM, zhiwei <zhiw...@gmail.com> wrote:
> Hi Kapil,
>
> There are two methods to build Mesos modules, one is using installed Mesos
> files, the other is using compiled Mesos files.
The second method is a hack because the first method is not foolproof.
Ideally, one should be able to build a module without having to
decipher the internal directory layout, etc., of Mesos build dir.
>
> Your proposal only affect the first method.
>
> I don't think packaging 3dparty libraries to Mesos is a good solution if
> the 3rdparty libraries have their own standard package(rpm or deb), we
> should document the 3rdparty libraries to let users install them.
That exactly is the problem. If the standard installed versions are
different (as noted in the follow up emails), it's not possible to
compile the module at all.
> Since picojson has not a standard package, so we can include it in Mesos.
> But for others, I prefer to let users install them when they need.
>
>
> Thanks,
> Zhiwei
>
> On Wed, Jan 20, 2016 at 6:03 AM, Kapil Arya <ka...@mesosphere.io> wrote:
>
>> Hi All,
>>
>> I wanted to get your opinion on installing the 3rdparty packages glog,
>> protobuf, boost and picojson[1] when installing Mesos itself. These
>> packages are required to build Mesos modules.
>>
>> Currently, a module write has to manually install these 3rdparty
>> packages, either system-wide or locally, and update the compilation
>> flags such as CPPFLAGS to point to the installation which is
>> error-prone. Further, one might have a system-wide installation with
>> the wrong package version, causing even more headache.
>>
>> The proposal here is to install these 3rdparty packages when
>> installing Mesos. To avoid any conflicts with system-wide or local
>> installation, we can install them as follows:
>>
>> ${PREFIX}/include/mesos/3rdparty -- for header files
>> ${PREFIX}/<LIBDIR>/mesos/3rdparty -- for library files (LIBDIR can be
>> lib or lib64 depending upon the installation)
>>
>> where PREFIX refers to the `--prefix` flag for Mesos configure script.
>>
>> We would then update `mesos.pc` with the correct flags so that a
>> module write can simply use `pkg-config` to get all the required
>> flags.
>>
>> I have created an issue
>> https://issues.apache.org/jira/browse/MESOS-4434 to track this.
>>
>> Best,
>> Kapil
>>
>>
>> [1]: picojson is currently installed in ${PREFIX}/include. See
>> https://issues.apache.org/jira/browse/MESOS-3909
>>
