public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: "Tevfik Karagülle" <tevfik@itefix.no>
To: <cygwin-licensing@cygwin.com>
Subject: Re: 1NIWGYC.DLL ??
Date: Mon, 19 Dec 2005 12:20:00 -0000	[thread overview]
Message-ID: <006f01c6047e$b68137f0$2602a8c0@itefixb> (raw)



> I don't know what you mean by "cygwin development environment" but,
> AFAIK, you are not developing the cygwin DLL.

What do you call if I use a cygwin environment for development and testing ?
Such environments should be separated from production environments where
Openshh/rsync could be used as elements. That's my point !!!

> downloading the latest version of the cygwin distribution and don't want
> to somehow destabilize your openssh setup then it seems like working
> with the setup.exe and openssh maintainers is the best way to accomplish
> this.

I can only say that there are (should be!!) other ways to do the same thing.
In addition, as I wrote in my previous post, the best solution would be to use 
a cygwin setup, which allows several separated environments. Platform
virtualization is a hot topic nowadays. Why can't cygwin also offer that 
functionality? 

> It really sounds like you are interested in providing workarounds for
> what you perceive to be problems with the cygwin distribution rather
> than working towards fixing the problems.

Sorry, I don't agree with you. Maybe, I fix some problems which have low
priority in your list. When it comes to workarounds, they will always exist.

> I suspect that your efforts will just serve to confuse people and so 
> I'm not happy with the way you are proceeding and I will certainly 
> publicly express my dissatisfaction the first time someone posts
> a question about "your" version of openssh and whatever-you-call-the-dll 
> on the cygwin list. 

Confusing people ? How can I do that with developing an installer installing
a fully operational openssh server and make it ready for use within one minute?
Disturbing your forums happened only once during the copssh lifetime. BTW,
The full blown cygwin installation had the same problem.

I've just tried to express a need. I feel that I don't deserve your comments above.

> So, yes, this is a GPL project and you can take the software, 
> rename it and massage it to do whatever you want with it.  That does not mean
> that it is the right thing to do or that your efforts will be appreciated by
> the people who are providing the software, however.

Both Copssh and Cwrsync are free software. As of december 2005, they are being
downloaded ca. 300 times daily and I get many mails from users expressing their 
appreciations. What's the right thing to do ? To continue with this effort? To express
a growing demand and a possible solution to cygwin developers ? I did it both !!!!

Tev


             reply	other threads:[~2005-12-19 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 12:20 Tevfik Karagülle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-16 20:50 Tevfik Karagülle
2005-12-18 17:10 ` Reini Urban
2005-12-18 19:01 ` Christopher Faylor
2005-12-16  2:19 Tevfik Karagülle
2005-12-16  2:57 ` Brian Dessent
2005-12-16  3:20   ` Christopher Faylor

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

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

  git send-email \
    --in-reply-to='006f01c6047e$b68137f0$2602a8c0@itefixb' \
    --to=tevfik@itefix.no \
    --cc=cygwin-licensing@cygwin.com \
    /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.
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).