From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libdmtx: add license information
Date: Tue, 7 Jan 2014 07:58:14 -0600 [thread overview]
Message-ID: <20140107075814.19ea98c9@core2quad.morethan.org> (raw)
In-Reply-To: <CA+-urNTa1LZ-95nFPNN=PMMChMNPSqE3zj64DZLix2TqrXhgTg@mail.gmail.com>
On Tue, 7 Jan 2014 08:48:37 -0500
Frank Hunleth <fhunleth@troodon-software.com> wrote:
> Hi Baruch,
>
> On Tue, Jan 7, 2014 at 12:35 AM, Baruch Siach <baruch@tkos.co.il>
> wrote:
> >
> > Hi Frank,
> >
> > On Mon, Jan 06, 2014 at 11:14:06AM -0500, Frank Hunleth wrote:
> > > Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>
> > > ---
> > > package/libdmtx/libdmtx.mk | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/package/libdmtx/libdmtx.mk
> > > b/package/libdmtx/libdmtx.mk index 69c7b88..43b35ec 100644
> > > --- a/package/libdmtx/libdmtx.mk
> > > +++ b/package/libdmtx/libdmtx.mk
> > > @@ -6,6 +6,8 @@
> > >
> > > LIBDMTX_VERSION = 0.7.4
> > > LIBDMTX_SITE =
> > > http://downloads.sourceforge.net/project/libdmtx/libdmtx/$(LIBDMTX_VERSION)
> > > +LIBDMTX_LICENSE = BSD-2c or Commercial license
> > > +LIBDMTX_LICENSE_FILES = LICENSE
> >
> > The "alternate terms" section in the LICENSE file states:
> >
> > > Redistributions in binary form, with or without modification, are
> > > permitted without including the above copyright notice, list of
> > > conditions, and disclaimer if express written permission has been
> > > obtained from Dragonfly Logic, Inc.
> >
> > I wouldn't call this written permission a "commercial license", but
> > IANAL.
>
> Yeah, I almost called it "alternate terms", but that felt too vague.
> It seemed like most other packages used the words "commercial license"
> when you could contact the author/company to get out of open source
> license obligations. However, if there's some other language that
> better describes this, then I'll certainly modify the patch. I just
> don't know what those words are.
>
> Thanks,
> Frank
>
BSD-2c or Special Permission
Those are the words, but "or Special Permission (of the author)" is
a null statement - it is always true.
Mike
> >
> > baruch
> >
> > > LIBDMTX_INSTALL_STAGING = YES
> > >
> > > $(eval $(autotools-package))
> > > --
> > > 1.8.3.2
> >
> > --
> > http://baruch.siach.name/blog/ ~. .~ Tk
> > Open Systems
> > =}------------------------------------------------ooO--U--Ooo------------{=
> > - baruch at tkos.co.il - tel: +972.2.679.5364,
> > http://www.tkos.co.il -
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2014-01-07 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 16:14 [Buildroot] [PATCH] libdmtx: add license information Frank Hunleth
2014-01-07 5:35 ` Baruch Siach
2014-01-07 13:48 ` Frank Hunleth
2014-01-07 13:58 ` Mike Zick [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=20140107075814.19ea98c9@core2quad.morethan.org \
--to=minimod@morethan.org \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.