Return-Path: Delivered-To: apmail-lucene-ruby-dev-archive@www.apache.org Received: (qmail 85039 invoked from network); 14 Feb 2007 02:57:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2007 02:57:01 -0000 Received: (qmail 53492 invoked by uid 500); 14 Feb 2007 02:57:08 -0000 Delivered-To: apmail-lucene-ruby-dev-archive@lucene.apache.org Received: (qmail 53475 invoked by uid 500); 14 Feb 2007 02:57:08 -0000 Mailing-List: contact ruby-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ruby-dev@lucene.apache.org Delivered-To: mailing list ruby-dev@lucene.apache.org Received: (qmail 53464 invoked by uid 99); 14 Feb 2007 02:57:08 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2007 18:57:08 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [69.55.225.129] (HELO ehatchersolutions.com) (69.55.225.129) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2007 18:56:57 -0800 Received: by ehatchersolutions.com (Postfix, from userid 504) id F19E230EFC17; Tue, 13 Feb 2007 21:56:36 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on javelina X-Spam-Level: Received: from [10.0.1.2] (va-71-53-203-135.dhcp.embarqhsd.net [71.53.203.135]) by ehatchersolutions.com (Postfix) with ESMTP id 99EDD30EFC16 for ; Tue, 13 Feb 2007 21:56:33 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <1D381BC8-8CA4-4D3A-82F0-6477DE99A8F6@pobox.com> References: <20F6FBED-F6EE-40F3-A2F7-8AE12887AB6D@pobox.com> <50CBBEEA-8F34-48BD-BA00-7EC930DA2EDB@ehatchersolutions.com> <774F0D3F-376A-4C93-93D3-01979CBD177F@pobox.com> <1D381BC8-8CA4-4D3A-82F0-6477DE99A8F6@pobox.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Erik Hatcher Subject: Re: solrb/flare in action? Date: Tue, 13 Feb 2007 21:56:28 -0500 To: ruby-dev@lucene.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_00, RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.1.1 On Feb 13, 2007, at 9:43 PM, Edward Summers wrote: > I can understand wanting to have code and packages hosted at > apache. But I don't seem what the problem is with at the same time > distributing the gem in a way that is familiar to the ruby > community at large. This is how rails is distributed for example > [1,2]. Certainly a good point about Rails itself. Again, I'm not trying to make things more complicated or unfamiliar to anyone. Let me spell out my ideal: gem install solrb and have that come from apache.org. If rubygems cannot currently handle this, then I'd like to push in that direction. It would require us to work on some infrastructure issues and get gems and their manifests deployed properly to be mirrored. But, let's move forward with the release planning rather than going back and forth with handwaving over the hassles apache.org deployment may present to Ruby developers. With what we've got, how do we deploy a gem to RubyForge? Who would be in charge of that and how would that coordinate with the official building of the release? Can we do this straight from rake? "rake release"? I'm all for us releasing to RubyForge given this discussion. And I'll try the parallel track of pushing the Apache infrastructure and rubygems modifications. Erik