savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] submission of NetHack Proxy - savannah.nongnu.org


From: Jonathan Gonzalez V.
Subject: Re: [Savannah-hackers] submission of NetHack Proxy - savannah.nongnu.org
Date: Wed, 24 Nov 2004 21:03:58 -0300
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)

address@hidden writes:

Hi J. Ali Harlow: 

I'm evaluating the project you submitted for approval in Savannah.

Can you send me the source code to my email (address@hidden)? 
I wish to review the source code, to catch potential legal issues
early. 

Regards,

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
>
>
> J. Ali Harlow <address@hidden> described the package as follows:
> License: other
> Other License: Joint GNU LGPL and NetHack General Public License
>
> nhproxy must be licensed under the NetHack General Public License so that
> it is useable by NetHack and its variants. By also releasing it under the
> LGPL we allow for the possibility of future windowing interfaces to be
> written under other licenses (including GPL). Since I wrote all the code
> in nhproxy, there is no problem to relicense it in this manner.
> Package: NetHack Proxy
> System name: nhproxy
> Type: non-GNU
>
> Description:
> nhproxy is a library to provide proxy support for windowing interfaces of
> NetHack and its variants. Without nhproxy, NetHack et. al. have a
> reasonably complete abstraction API for windowing interfaces which has
> been used for a number of years to provide windowing interfaces on a
> variety of platforms (including Gnome and Gtk+). nhproxy is to NetHack et.
> al. just another of these interfaces. Windowing interfaces which are
> written to use nhproxy can be built as self-contained executables which
> connect to NetHack et. al. either by forking and executing a program on
> the local computer or via TCP/IP to a server running a version of NetHack
> et. al. configured with nhproxy.
>
> Up to this point, nhproxy has been developed as part of the Slash'EM
> project. (a NetHack variant). It has now reached the stage that it would
> be good to unbundle it. This would allow easier integration into other
> NetHack variants and windowing interfaces which are not part of Slash'EM.
> It will also allow for the possibility to write windowing interfaces which
> are covered by a license compatible with LGPL (the current situation is
> that nhproxy is covered by the NetHack General Public License which is
> required when used with NetHack et. al. but limiting when used with
> windowing interfaces).
>
> You can browse the current version in Slash'EM CVS starting at:
>
> http://cvs.sourceforge.net/viewcvs.py/slashem/slashem/win/proxy/
>
> (there are also some include files in slashem/include).
>
> I am currently in the process of unbundling nhproxy and porting to
> autoconf at which point I plan to release a snapshot. I hope to complete
> this before Christmas, but would prefer not to wait for this before having
> the savannah project registration completed if possible. 
>
>
> Other Software Required:
> nhproxy will not depend on anything. The initial (pre v1.0) snapshorts
> will have an implicit dependency on Slash'EM. That is, nhproxy will build
> without Slash'EM but in order to use it windowing interfaces need to know
> the values of a number of pre-processor tokens that are defined in
> Slash'EM headers. Removing this dependency will be one of the major tasks
> in preparing the version 1.0 release.
>


-- 
"Emacs the only editor which has its own church"

Attachment: pgpirHd6y2SSL.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]