I agree – I also don't have to maintain this alone. Once this is working as expected, I wanted to push the build stuff into a repo where more people have access to and we could also created a 'team' on launchpad to have more people contribute to this (or at least be able to).
Till On Monday, June 11, 2012 at 3:06 PM, Jan Lehnardt wrote: > A patch and/or a repo somewhere would be nice :) > > On Jun 11, 2012, at 09:08 , CGS wrote: > > > Hi, > > > > I isolated the tests which are started with make check and make them run > > over the default installation under Ubuntu 12.10. Please, let me know if it > > is what you need (there is a README file in the archive). > > > > CGS > > > > > > > > > > > > On Sun, Jun 10, 2012 at 8:46 PM, till <[email protected] > > (mailto:[email protected])> wrote: > > Hey, > > > > [ CC'd user@ to get more feedback. ] > > > > I made some progress. > > > > I have builds for the following more or less ready: > > > > * karmic > > * lucid > > * maverick > > * oneiric > > * natty > > * precise > > > > It's building and I am trying to refine the process a bit. So it might > > break in between [aka WIP]. I'm just adding this as a disclaimer. > > > > https://launchpad.net/~till-php/+archive/couchdb > > > > Would you mind testing my builds? :) So far, I only tested lucid briefly > > (and ran into the xulrunner issue, which I think I have auto-fixed now). > > Besides I just started it up, created a DB and entered some docs into it. > > > > (Also, @Jan:) > > > > I'm trying to figure out how to setup more automated testing. "make check" > > always requires the source tree to be present, I'd like "make check" > > against my installed binaries. I saw the "verify installation" in Futon – > > something like that for the command line so I can iterate on these builds > > and trigger a "test this" in a continuous integration setup. Building is > > part of it, but since building a binary and installing it are two separate > > steps I want to ensure that the second step also works. I am still trying > > to wrap my head around a setup where I can maybe knife up a few instances > > in THE CLOUD, install my package, run its test-suite and confirm. > > > > Till > > > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote: > > > > > Hi, > > > > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running. > > > Unfortunately, I've never built a deb package, so, I cannot provide such a > > > package. Nevertheless, if you have any problem in building it, just let me > > > know and I will try to help. > > > > > > About the mailing list, I suppose adding the CouchDB users (to get an idea > > > which is the desired Ubuntu distro) and/or Debian (you may get support in > > > testing and debugging) lists wouldn't be such a bad idea, but it's your > > > call here. > > > > > > CGS > > > > > > > > > > > > > > > On Sat, Jun 9, 2012 at 9:15 PM, till <[email protected] > > > (mailto:[email protected])> wrote: > > > > > > > Hey, > > > > > > > > I've been scratching my own itch and started building 1.2.0 for a couple > > > > Ubuntu distributions. > > > > > > > > It's a WIP but I was wondering the following: > > > > > > > > 1) It builds – but does it work? Is the best bet to run the test suite > > > > in > > > > futon, or is there something I could run on the command line when the > > > > package is installed? I'd prefer the command line to include it in some > > > > sort of continuous testing without a browser. > > > > > > > > 2) Who'd have some interest in testing this? > > > > > > > > 3) Which distributions are wanted – I started with karmic and lucid and > > > > had planned to build all the way up to 12.10. > > > > > > > > 4) Is there a mailing list to discuss this, or is dev@ fine? > > > > > > > > Till > > > > > > <couchdb_etap.tgz>
