* Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>> Steve Youngs <youngs_s(a)ozlinx.com.au>
writes:
Steve> My package, which is an ICQ client for XEmacs, needs an
Steve> external binary program to run. The external binary is a
Steve> UDP to TCP bridge. Unfortunately, at the moment it will
Steve> only run on Linux (x86)[1].
Steve> See the dilemma?
No. If it's not free software, we won't distribute it. If
it is, we
can.
It is free software, so, in your eyes it's not a dilemma?
If it is really quite Emacs-specific, it would go in ./lib-src. If
the UDP-to-TCP bridge seems more generally useful, create a project on
SourceForge, and we can put a version in ./lib-src is that seems
necessary. Either way, it will probably get ported (and quickly;
people can't seem to live without ICQ, whatever that is ;-).
Well at the moment I have no interest in doing anything with it except
for using it for ICQ in XEmacs, so I guess that would make it pretty
well Emacs-specific. I have put it in ./lib-src (figured that would
be the best place for it).
Should I just submit the package as is and mark the description "For
Linux x86 only - please port me"?
The work to do it as an Emacs module would be appreciated, but that
can't change any system dependencies.
Would there be any advantages to having it as a module? Or would it
just be a waste of time?
--
|---<Regards, Steve Youngs>-----------[GnuPG KeyID: EFD82ED2]---|
| It's a funny thing about life; if you refuse to accept |
| anything but the best, you very often get it |
|-----------------------------<mailto:youngs_s@ozlinx.com.au>---|