public inbox for
 help / color / mirror / Atom feed
From: Jim Blandy <>
Subject: RDA on Solaris and Win32
Date: Wed, 08 Dec 2004 19:23:00 -0000	[thread overview]
Message-ID: <vt2d5xkzjbp.fsf@zenia.home> (raw)

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.

             reply	other threads:[~2004-12-08 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 19:23 Jim Blandy [this message]
2004-12-08 20:13 ` Kevin Buettner
2004-12-13 20:31   ` Christopher Faylor
2004-12-14 16:49     ` Jim Blandy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vt2d5xkzjbp.fsf@zenia.home \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).