mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kapil Arya (JIRA)" <>
Subject [jira] [Commented] (MESOS-5608) Apache Pre-Compiled Tarballs
Date Mon, 13 Jun 2016 21:22:03 GMT


Kapil Arya commented on MESOS-5608:

Hi Hari,

The numbered suffixes are a well-known scheme to track the packaging software. However, I
do agree that Mesosphere suffix are a little more complicated to figure out. I would recommend
using the page to learn about the exact filenames.
Also, if you can use yum/apt-get, then the instructions provided at
would allow you to update/install mesos packages without having to know the exact version

We are thinking/planning for a better package build infrastructure that we can potentially
share with the community. I'll post the updated once I have any.


> Apache Pre-Compiled Tarballs
> ----------------------------
>                 Key: MESOS-5608
>                 URL:
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Hari Sekhon
>            Priority: Minor
> Request for pre-compiled tarballs on the apache download mirrors and
for older versions.
> I used to compile this myself but nowadays I use Docker builds a lot and don't want to
be forced to have lots of dev build tooling bloating my docker images to build this from source.
> Most other apache projects provide both the source tarball as well as precompiled tarball.
> I've used Mesosphere's downloads as they provide rpms + debs but the problem is their
URLs have non-deterministric build suffixes appended to each version so that I cannot build
or update across versions without hardcoding the almost random build suffixes for every minor
version change as I can't predict the build suffixes.
> Normal apache tarballs with consistent names seems like something common to Apache projects
that the Mesos project is currently missing.
> Thanks
> Hari

This message was sent by Atlassian JIRA

View raw message