re: Red Hat packaging. I can help Sheppard it, and have opened MESOS-543 as a start. When the time comes we can kick-start the channels (Fedora || EPEL) when it gets further down the road. Ideally helping to promote adherence to certain guidelines enables down-streams to easily package, and we can promote co-maintainers for the channels as they are typically community driven.
Cheers, Tim [Red Hat "Roman" ;-)] ----- Original Message ----- > From: "Daniel Lundin" <[email protected]> > To: [email protected] > Sent: Thursday, July 11, 2013 3:47:17 PM > Subject: Re: Merging in packaging tools for Mesos > > Hey guys, > > As an option, I've attached the debian packaging patch I've used for > packaging Mesos for Ubuntu (Precise) to MESOS-74. It does not use a third > party / unified packager, rather just the standard toolchain - A debian > directory in the source tree with all the trimmings. Just run "debuild ..." > at the top and, ideally, you're good to go. > > Overall, in my experience it's hard to maintain packages for multiple > platforms using a "meta-packager" scheme on a sizeable/multi-language > project. It's usually easier to just go with the romans, whomever they may > be at that particular juncture. Different systems have different policies > for packages, how to split them up (libs, dev, language-specific bits), > dealing with multi-architecture, python versions, etc. I've always ended up > with *more* work trying to unify system packaging than just doing it once > per platform. :) > > It might be worth considering it can be easier to find people experienced, > interested and opinionated in platform-specific packaging, and the work > tends to be low-hanging fruit for contributing to a project. > > In any case, hope the patch comes in handy. > > Cheers, > /d > > > > On Wed, Jul 10, 2013 at 7:50 PM, Benjamin Hindman > <[email protected]>wrote: > > > +1! > > > > > > On Wed, Jul 10, 2013 at 10:48 AM, Vinod Kone <[email protected]> wrote: > > > > > Hey Jason and Tomas, > > > > > > Love it! We definitely like to include this in the mesos repo. Would you > > > mind sending out the patch(es) via Apache ReviewBoard? That is our > > > preferred way to review changes before committing them. > > > > > > P.S: Since mesos graduated, the new repo location is: > > > https://git-wip-us.apache.org/repos/asf/mesos.git > > > > > > Thanks, > > > > > > > > > On Wed, Jul 10, 2013 at 10:27 AM, Jason Dusek <[email protected]> > > > wrote: > > > > > > > Dear List, > > > > > > > > I have been working on automated packaging for Mesos on Debian > > > > and Ubuntu. > > > > > > > > https://github.com/solidsnack/mesos-deb-packaging/ > > > > > > > > Much thanks is due to Tomas Barton, who got the ball rolling on > > > > this and put together much of the code in the repo above. > > > > > > > > The present collection of init scripts and build options is used > > > > regularly for automated rollouts of Mesos at my firm, on Debian > > > > and Ubuntu, in conjunction with tools using the Java API. We are > > > > looking in to proper installation and setup of the Python > > > > libraries. > > > > > > > > The `build_mesos' script is useful for those wishing to build > > > > and release internal forks of Mesos, too. > > > > > > > > Support for RedHat/CentOS is important to us and is planned for > > > > the near future. We'd like to see Mesos make its way in to the > > > > repositories someday. What we have is a solid foundation and it > > > > seems like integrating with mainline Mesos early is the best way > > > > to make for a smooth transition in the future. > > > > > > > > Would it be alright to add this material to > > > > > > > > http://git.apache.org/incubator-mesos.git > > > > > > > > under a new directory, "packaging"? This tooling will eventually > > > > grow to encompass Homebrew as well as RPMs so its probably just > > > > as well to keep the name distro agnostic. > > > > > > > > -- > > > > Jason Dusek > > > > pgp // solidsnack // C1EBC57DC55144F35460C8DF1FD4C6C1FED18A2B > > > > > > > > > >
