Bug#760315: ITP: mesos -- Cluster manager for sharing distributed application frameworks
On 16.08.2015 05:02, Dmitry Smirnov wrote:
> Hi Daniel,
>
> It is great to see that you are working on packaging Mesos. For some time
> already I was also fiddling with its packaging but was (and still) reluctant
> to take over the RFS... It seems that Mesos have systematic issues with
> versioning of the libraries from "libmesos" all the way down to "libprocess"
> and "libgmock". Because of this it might be best to refrain from packaging
> standalone "libprocess" and use its bundled copy (statically linked or
> installed to private location) until this problem is fixed upstream.
>
> My Mesos packaging is in very early draft stage but I might be able to
> contribute few things if you consider working in public repository (i.e. at
> collab-maint, etc.).
>
> Also due to burden of bundled upstream dependencies I recommend to use
> shallow ("debian/*" only) repository layout like the one that KDE team uses:
>
> https://pkg-kde.alioth.debian.org/gitguidelines.html
>
> Thank you.
Hi Dmitry,
I going to fix a couple of smaller packages from my WNPP stack before, but I am
very interested in this.
Thank you for the pointer on the libraries issue here, I'll keep that mind when
I get into it, probably I'll approach you on this again, then.
Yes, great, if you would like to share your preliminary work that would be
very much welcome! I'll keep that in deb/copyright.
And ... yes, I'm all right with a repo outline like this, let's do it that way.
Greetings,
Daniel
--
http://www.danielstender.com/blog/
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Reply to: