From: Ross Johnson <rpj@callisto.canberra.edu.au>
To: Seshubabu Pasam <pasam@seshubabu.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: License info
Date: Mon, 17 May 2004 05:50:00 -0000 [thread overview]
Message-ID: <40A852D9.5020302@callisto.canberra.edu.au> (raw)
In-Reply-To: <40A71079.6070503@seshubabu.com>
Hi,
One way to answer this is to say that you may include all of the files
with your distribution if you like.
However, if you want to minimise the number of these files you need to
include, then the very least you need to do is (IMO):
- include the pthreads-win32 copyright notice as described in the file
COPYING along with your own copyright.
- I think it would be polite, if not required, to include the file
COPYING. This is a wrapper for the GNU LGPL contained in the file
COPYING.LIB and it covers a few minor things in pthreads-win32 that the
LGPL doesn't cover, such as a few files that are excepted from the LGPL,
such as one of the test application files.
- Likewise for the file COPYING.LIB. Because this file is referenced in
other files, it should probably not be renamed, however it should be
made clear that it relates to pthreads-win32.
- provide information telling recipients where they can find the source
code, preferably from your own web or ftp site if it isn't included in
your distribution.
Here's a link to a web page that looks like it's part of the online
documentation for various Rational software packages.
http://www.isy.vcu.edu/rational/documentation/doc/legal_information.html
It's probably a good example of how it should be done. It includes a
reference to pthreads-win32 as well as a multitude of other third-party
components that they've incorporated. See under the heading
'Rational Test Manager, Rational Quality Architect, Rational Robot,
Rational TestSuite'. They also appear to include the pthreads-win32
source code in their distribution.
Regards.
Ross
Seshubabu Pasam wrote:
>
> Hi there,
>
> We are looking into using pthread-win32. Which pthread-win32 files are
> we supposed to redistribute with our product? COPYING or COPYING.LIB
> or both? Also are we required to distribute this file(s) separately?
> Or can we copy them into our documentation? Or better yet, provide URL
> links to these files in our documentation?
>
> May be this is not the right group, but probably some of you are
> already using this library and can advise me.
>
> -Thanks & Regards
> Seshubabu Pasam
>
prev parent reply other threads:[~2004-05-17 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 6:56 Seshubabu Pasam
2004-05-17 5:50 ` Ross Johnson [this message]
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=40A852D9.5020302@callisto.canberra.edu.au \
--to=rpj@callisto.canberra.edu.au \
--cc=pasam@seshubabu.com \
--cc=pthreads-win32@sources.redhat.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).