From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs on Mac OS X
Date: Wed, 06 Apr 2005 00:28:35 +0200 [thread overview]
Message-ID: <x5wtrgluy4.fsf@lola.goethe.zz> (raw)
In-Reply-To: <45CB1EC6-3068-4634-85FA-57BB9F56E8DB@cian.ws> (Cian Hughes's message of "Tue, 5 Apr 2005 22:10:18 +0100")
Cian Hughes <cian@cian.ws> writes:
> Hi, I'm currently running Mac OS X 10.4 which is currently
> unreleased commercial software, so having agreed to an NDA I really
> have no right to ask for your help.
The problem is rather that you have no right to _offer_ your help.
What goes into Emacs, is released openly as free software. So you are
subjecting yourself to lawsuits from Apple if you contribute to Emacs.
> However I have discovered a very serious issue with emacs on Mac OS
> X 10.4 (tiger) and due to a change in carbon, emacs (latest CVS
> version as of today) does not compile. I have enough experience with
> Mac OS X to try and fix the problems which I would obviously send to
> you immediately, however before I invest my time in this (there are
> lots of other broken things under Tiger) I just thought i'd enquire
> as to who is currently maintaining mac.c and the carbon bridge for
> emacs, I have tried asking Andrew Choi who used to do this, but he
> was unable to help. If there is nobody maintaining the bridge let me
> know & i'll get to work. I will find time to repent for my NDA
> related sins at a later time, but at the moment my primary concearn
> is that when Tiger hits the world emacs will compile on it when
> configured --with-carbon --without-x.
Your NDA might mean that Apple, not we, is prohibiting you from making
that happen. Contributing to Emacs means disclosure (and you agreed
to non-disclosure): everything is freely available.
> I will happily discuss the problems with the relevant developers, I
> hope we can solve this soon.
The party you have to discuss your problem with is Apple. You have
signed a presumably legal binding agreement to them, not us, that you
would not contribute your information to an open project like Emacs.
So you have to explain your cause to them and ask for special
permission from them. The Emacs developers can't absolve you from
your promises to Apple.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2005-04-05 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f9501fdd7bb0af966d1ef30bcb89d0b6@shaw.ca>
2005-04-05 21:10 ` Emacs on Mac OS X Cian Hughes
2005-04-05 22:28 ` David Kastrup [this message]
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=x5wtrgluy4.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).