Return-Path: Delivered-To: apmail-hadoop-avro-dev-archive@minotaur.apache.org Received: (qmail 21555 invoked from network); 16 Oct 2009 08:16:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Oct 2009 08:16:54 -0000 Received: (qmail 1977 invoked by uid 500); 16 Oct 2009 08:16:54 -0000 Delivered-To: apmail-hadoop-avro-dev-archive@hadoop.apache.org Received: (qmail 1903 invoked by uid 500); 16 Oct 2009 08:16:54 -0000 Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: avro-dev@hadoop.apache.org Delivered-To: mailing list avro-dev@hadoop.apache.org Received: (qmail 1893 invoked by uid 99); 16 Oct 2009 08:16:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Oct 2009 08:16:54 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.85.222.195] (HELO mail-pz0-f195.google.com) (209.85.222.195) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Oct 2009 08:16:46 +0000 Received: by pzk33 with SMTP id 33so1554367pzk.2 for ; Fri, 16 Oct 2009 01:16:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.61.33 with SMTP id j33mr112469wfa.236.1255680985105; Fri, 16 Oct 2009 01:16:25 -0700 (PDT) From: Matt Massie Date: Fri, 16 Oct 2009 01:16:05 -0700 Message-ID: <35538fbe0910160116p19592d5ah85a04608e52ee8aa@mail.gmail.com> Subject: Request for feedback regarding distribution of Avro C code To: Avro Developers Content-Type: multipart/alternative; boundary=001636e1f93d11864f047609032f X-Virus-Checked: Checked by ClamAV on apache.org --001636e1f93d11864f047609032f Content-Type: text/plain; charset=ISO-8859-1 My experience has been that bolting autotool projects to ant projects causes *tons* of grieve for developers and consumers alike. Originally, I packaged the C code the way I've seen it done for other Hadoop projects even though I don't agree with the approach. Now, I'd like to do things differently if the team agrees. I propose the following: (1) Leave the "cdoc" and "package-c" targets in build.xml but remove all other C targets (e.g. configure-c, compile-c). This will allow us to continue generating documentation and packaging the C code from ant. (2) Change the "package-c" target to run autotool's 'make distcheck' to create a distributable tarball (called avro-c-x.x.x.tar.gz). People familiar with compiling native code will know to extract the tarball and then run "./configure;make". Creating this tarball with autotools will ensure that all the necessary files exist (with the correct permissions), that 'make install uninstall' works without leaving files behind, remove any dependency on autotools, etc. (3) Instead of having a "Linux-i386-32" directory inside the top-level 'c' directory, users will find a ready-to-use avro-c-x.x.x.tar.gz C package and a README file People who want to work on the C source in svn/git will very likely be familiar with how to manage autotools and this setup wouldn't prevent them from happily hacking away. Developers and users both would be happy and we wouldn't have to abuse ant and autotools in the process. -Matt --001636e1f93d11864f047609032f--