> In its pretty form, this is pretty hard to work with. If there > is anyway you could create branch on GitHub...
Absolutely, here's the very branch whence it came: https://github.com/dln/incubator-mesos/tree/debian-package Should be a bit easier to read. :) I noticed when double-checking today it's a bit incomplete, specifically missing a dependency on a jdk (for libjvm). I'll go ahead and fix this. > An open question for the project is how we want to manage Mesos > configuration. +1. Config file, env vars *and* flags is probably two options too many. Personally, I'm all for only using environment vars and removing "/etc/mesos/mesos.conf" altogether. Maybe have defaults in /etc/default/mesos and also sourcing /etc/mesos/mesos-env.sh for "user settings"? /d On Fri, Jul 12, 2013 at 9:13 PM, Jason Dusek <[email protected]> wrote: > 2013/7/11 Daniel Lundin <[email protected]>: > > 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. :) > > This really seems right to me. The meta package manager might > get you something the installer will accept; but not something > the distro will accept. > > > 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. > > In its pretty form, this is pretty hard to work with. If there > is anyway you could create branch on GitHub... > > Of course I will still try to read it over the weekend, anyways. > > An open question for the project is how we want to manage Mesos > configuration. In the branch I'm working on, it's all > environment variables; and /etc/mesos/zk is loaded into an > environment variable and is the only "config file". We could > have a `mesos.conf' but as far as I understand it, file-based > config is slated for removal. > > -- > Jason Dusek > pgp // solidsnack // C1EBC57DC55144F35460C8DF1FD4C6C1FED18A2B >
