From: "Gareth Pearce" <tilps@hotmail.com>
To: cygwin@cygwin.com
Subject: Re: another cygwin using program...
Date: Wed, 10 Jul 2002 01:58:00 -0000 [thread overview]
Message-ID: <F117TiXLl7xukvO4vJJ00008d15@hotmail.com> (raw)
>
>On Wed, Jul 10, 2002 at 06:02:55AM +0000, Gareth Pearce wrote:
> >>> > > http://freeware.teledanmark.no/identd/
> >>> > > uses cygwin1.dll - and might not be providing source ... I
> >>> > > cant find it...
> >>> >
> >>> >You didn't look very hard. Source is included in the same
> >>> >archive as the executable.
> >>>
> >>> cygwin1.dll source to be specific
> >>
> >>Sorry. That wasn't clear.
> >>
> >>> I did indeed find the source to identd in the obvious place.
> >>
> >>Yep. And they point to Cygwin, but thier alternate site for Cygwin has
>the
> >>old B20 version. Will thier code build against the current version of
>the
> >>DLL? If not, they aren't in compliance with the GPL.
> >>
> >
> >previous mailing list discussions on this topic state that if they
> >distribute the cygwin1.dll, they have to distribute the source code for
>that
> >
> >particular version.
>
>You are correct, sir.
>
> >So either way its a violation. (ie linking isnt good enough, according to
> >previous discussions) - I am still in digital unix at uni so i have no
>idea
> >if it compiles with current cygwin, anyway.
> >
> >But, it was a headsup, not a 'i am deeply concerned about this' or I
>would
> >of emailed the person responsible for the web site in the first place.
>If i
> >was one of the cygwin developers, maybe i would feel differently, but as
>a
> >user headsup is enough from me.
>
>Yep. I wouldn't want to subject a user to the pain of sending this kind of
>email. Seriously. It's never fun.
>
>I'll probably send something off as soon as I can ensure that my spirit is
>pure and my will is strong.
>
>Thanks for the heads up. It is appreciated. Keem em coming.
>
>cgf
<sarcasm off>
lol
always a great wit there - the bridge one earlier had the office and the mud
laughing :)
but 'seriously' i just dont care enough to send one onwards to the person.
But, I think it is just wrong, to not let the people who Might care, know.
Wierd point of view, yes
but thats me.
<sarcasm back on>
Gareth - seriously going to start work on a new release of nano any day now
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-07-10 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 1:58 Gareth Pearce [this message]
2002-07-10 9:50 ` Christopher Faylor
2002-07-10 20:51 ` Gareth Pearce
-- strict thread matches above, loose matches on Subject: below --
2002-07-11 0:21 Karl M
2002-07-10 13:52 morad m
2002-07-10 14:19 ` Charles Wilson
2002-07-09 23:28 Gareth Pearce
2002-07-09 23:29 ` Christopher Faylor
2002-07-09 22:02 Gareth Pearce
2002-07-09 21:12 Gareth Pearce
2002-07-10 9:23 ` Nicholas Wourms
2002-07-10 13:49 ` Michael Schaap
2002-07-10 21:18 ` Christopher Faylor
2002-07-10 21:42 ` Charles Wilson
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=F117TiXLl7xukvO4vJJ00008d15@hotmail.com \
--to=tilps@hotmail.com \
--cc=cygwin@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).