This is the mail archive of the
cygwin-licensing
mailing list for the cygwin project.
Re: 1NIWGYC.DLL ??
On Thu, Dec 15, 2005 at 06:35:24PM -0800, Brian Dessent wrote:
>Tevfik Karag?lle wrote:
>>on the target machine. However, It is tempting to find an ultimate
>>solution to this problem: renaming dlls and registry references. I
>>have tested and verified that it is technically possible.
>
>Just renaming the DLL and registry keys is not enough to avoid
>conflicts with an existing cygwin1.dll. You will also have to modifiy
>the name of the shared memory region and all other shared objects.
Right, and cygwin programs run by this forked version of openssh/cygwin
in an interactive session will not know they are running in a pty and
will work strangely. So, if the intent is to interoperate with cygwin
then this isn't a great plan.
It seems like there is no benefit to this distribution if the user is
running cygwin anyway. If they are running cygwin then they should just
use the openssh that comes with cygwin.
>From a licensing point of view you can do anything you want as long as
>you provide the source packages to build the binaries. AFAIK. IANAL.
>etc.
What he said. The GPL doesn't say anything about renaming files.
If this is really important, wouldn't it be better to work on providing
a minimal openssh setup via a category in the current cygwin setup.exe?
IMO, repackaging other people's stuff will usually lead to extra work
for the repackager and confusion for the end user.
Cygwin is a community project. You can make changes if you're
persuasive enough and if you have the proper skills.
cgf