unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Suggestion: remove s/sco[45].h etc.
Date: 21 Nov 2003 00:36:39 +0100	[thread overview]
Message-ID: <x5smkiipdk.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3ad6q62pu.fsf@kfs-l.imdomain.dk>

storm@cua.dk (Kim F. Storm) writes:

> Considering recent events, I don't see any point in actively
> supporting any of the SCO "owned" systems.
> 
> I suggest that we remove the corresponding support files, that is
> s/sco4.h and s/sco5.h, as well as other s/*.h files for other sysV /
> usg derivates created or owned by SCO.
> 
> WDYT?

It is one thing to actively support a system.  It is another to
actively sabotage any effort of people depending on that kind of
system to use free software.

It is my recommendation to free software maintainers not to spend any
effort of their own on supporting proprietary systems such as SCO
Unix variants.

But if people go to all the effort of providing all the work for
supporting a platform, I don't see the point in denying them access to
free software just because they are using (and perhaps compelledly so)
some unrelated proprietary software.

Please note also that Microsoft Windows is supported as an operating
platform for Emacs, and Microsoft certainly has been spreading as much
false information about free software as the current SCO-initiated
misinformation campaign is.

The way to spread freedom is not by denying it to people having to
live under restraints already.

Emacs use is contagious, anyway:  Emacs users on proprietary systems
basically fall into the two categories

a) works with free software whenever he can, is forced to work on
proprietary platforms at some time.
b) is getting infected with Emacs, will eventually migrate to a
platform where Emacs runs best, namely some GNU system.

People of category a) are often inspiring people to try out b).

So in short: I don't think it reasonable to block one of the
most compelling migration paths to free systems, for the sake of some
petty revenge thinking.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2003-11-20 23:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 23:26 Suggestion: remove s/sco[45].h etc Kim F. Storm
2003-11-20 23:36 ` David Kastrup [this message]
2003-11-20 23:47 ` Ted Lemon
2003-11-21  0:27 ` Eric Hanchrow
2003-11-21 11:59   ` Kim F. Storm
2003-11-21 13:05     ` David Kastrup
2003-11-22  0:09       ` Kim F. Storm
2003-11-22 21:19 ` Richard Stallman

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=x5smkiipdk.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).