From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19033 invoked by alias); 8 Dec 2004 19:23:22 -0000 Mailing-List: contact rda-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: rda-owner@sources.redhat.com Received: (qmail 18979 invoked from network); 8 Dec 2004 19:23:18 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 8 Dec 2004 19:23:18 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iB8JNIOZ005447 for ; Wed, 8 Dec 2004 14:23:18 -0500 Received: from zenia.home.redhat.com (sebastian-int.corp.redhat.com [172.16.52.221]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iB8JN6r06231; Wed, 8 Dec 2004 14:23:07 -0500 To: rda@sources.redhat.com Subject: RDA on Solaris and Win32 From: Jim Blandy Date: Wed, 08 Dec 2004 19:23:00 -0000 Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-q4/txt/msg00038.txt.bz2 Hmm. It seems that, although RDA includes code for Cygwin and Solaris, that code is not actually built by default when one configures the tree in the normal way on those platforms. All you get is the librda library. This means that we can't know if regenerating the auto* files introduces additional build problems for that platform-specific code without first making RDA actually build it again. I don't want to extend the scope of my project to include making the Cygwin and Solaris native support code build again. But evolving the surrounding support will inevitably bit-rot that stuff. It's the classic "unmaintained code" dilemma. Ideally, that stuff were made to build again, but limiting ourselves to actions we can afford to take immediately, what should our policy be? Here are the options I see, listed in order of decreasing preference for me: a) Declare Cygwin and Solaris native support to be unmaintained in the README file, but leave the sources in the tree. b) Delete the Cygwin and Solaris native support. If someone wants to resurrect it, it's all in CVS. c) Put off upgrading the auto* files until Cygwin and Solaris native build again and the upgrade can be tested. How do other folks feel? In January, I'm going to have some time available to make a web page for RDA and put together a release. I don't know if there will be any public interest in RDA, but if there is, we might find volunteers to work on the Solaris and Cygwin ports.