Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jun 2005 08:58:40 +0200
From:      Roland Smith <rsmith@xs4all.nl>
To:        Chris Palm <cpalm@global.t-bird.edu>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Building applications on BSD software
Message-ID:  <20050624065840.GA83250@slackbox.xs4all.nl>
In-Reply-To: <42BBA457.9050601@global.t-bird.edu>
References:  <42BBA457.9050601@global.t-bird.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

--fUYQa+Pmc3FrFX/N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 23, 2005 at 11:12:39PM -0700, Chris Palm wrote:
> Hello,
>=20
> I am writing a b-school paper on the use of open source software=20
> components and libraries used in and distributed with a company's=20
> applications, and the legal copyright and other business issues that aris=
e.
>=20
> What kinds of distribution requirements in terms of licensing would be=20
> in place around distributing one of BSD's libraries? If a company was to=
=20
> want to leverage and distribute these libraries with its products, what=
=20
> would that company have to do?

Let me start by saying that IANAL.

For stuff that comes under the revised BSD license, see
http://www.freebsd.org/copyright/freebsd-license.html

In short:
 - keep the copyright notice etc. in the code.
 - add a copy of the license to the distribution.

GPL or LGPL stuff is different, see below.

> Would you be willing to share a licensing agreement for BSD components?

The BSD license _is_ the license you need, AFAIK. You have a valid
copyright license as long as you comply with the terms of the license.

> I found your legal page, but was unclear as to whether a third party=20
> developer would use the the GNU or not.

If it's unclear, that's because the choice depends on what code you want
to use. You have to comply with the licensing terms in any case.

So if you want to incorporate GPL code in a product you want to
distribute externally, you practically must license your own product
under the GPL. See http://www.freebsd.org/copyright/COPYING

If you want to link your product to an LGPL library ('mere aggregation' in
terms of the LGPL), you can license your product as you please. See
http://www.freebsd.org/copyright/COPYING.LIB

BSD stuff is more or less 'no strings attached'.

HTH, Roland
--=20
R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text.
public key: http://www.xs4all.nl/~rsmith/pubkey.txt

--fUYQa+Pmc3FrFX/N
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCu68gEnfvsMMhpyURAuqHAJ9jVCI/9LIKDZZKkCu0Wq4Qkb4C/gCcDiz+
GNaminQRD7qXLfoc2ro6S2E=
=+zPp
-----END PGP SIGNATURE-----

--fUYQa+Pmc3FrFX/N--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050624065840.GA83250>