From: Leo Famulari <leo@famulari.name>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 48217@debbugs.gnu.org
Subject: [bug#48217] [PATCH 0/9] Add sdrangel
Date: Tue, 4 May 2021 12:38:30 -0400 [thread overview]
Message-ID: <YJF4hg8wm9yC+LKI@jasmine.lan> (raw)
In-Reply-To: <87czu6rimc.fsf@yamatai>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
On Tue, May 04, 2021 at 08:46:51AM +0000, Guillaume Le Vaillant wrote:
> --8<---------------cut here---------------start------------->8---
> While DSDcc is intended to be patent-free, `mbelib` that it uses
> describes functions that may be covered by one or more U.S. patents
> owned by DVSI Inc. The source code itself should not be infringing as it
> merely describes possible methods of implementation. Compiling or using
> `mbelib` may infringe on patents rights in your jurisdiction and/or
> require licensing. It is unknown if DVSI will sell licenses for software
> that uses `mbelib`.
> --8<---------------cut here---------------end--------------->8---
>
> Even if mbelib is free software, I guess the U.S. patent on the
> AMBE standard [1] prevents it from being included in Guix.
> What do you think?
I don't that these patents prevent inclusion. At least, we've never
worked that way in the past.
The question of whether or not a program / package "may be covered by
one or more U.S. patents" is not something that can be known until you
get sued by a patent owner and lose the case (or settle it). It applies
to literally every piece of software.
Basically, if you are making a lot of money with software, then you will
learn which patents you have used, based on the lawsuits filed against
you.
I'm no expert but that's my understanding.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-05-04 16:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:46 [bug#48217] [PATCH 0/9] Add sdrangel Guillaume Le Vaillant
2021-05-04 8:56 ` [bug#48217] [PATCH 1/9] gnu: Add csdr Guillaume Le Vaillant
2021-05-04 8:56 ` [bug#48217] [PATCH 2/9] gnu: Add serialdv Guillaume Le Vaillant
2021-05-04 8:56 ` [bug#48217] [PATCH 3/9] gnu: aptdec: Update to 1.7-1.5f91799 Guillaume Le Vaillant
2021-05-04 8:57 ` [bug#48217] [PATCH 4/9] gnu: Add cm256cc Guillaume Le Vaillant
2021-05-04 8:57 ` [bug#48217] [PATCH 5/9] gnu: Add libdab Guillaume Le Vaillant
2021-05-04 8:57 ` [bug#48217] [PATCH 6/9] gnu: Add sgp4 Guillaume Le Vaillant
2021-05-04 8:57 ` [bug#48217] [PATCH 7/9] gnu: Add sdrangel Guillaume Le Vaillant
2021-05-04 8:57 ` [bug#48217] [PATCH 8/9] gnu: Add dsdcc Guillaume Le Vaillant
2021-05-04 8:57 ` [bug#48217] [PATCH 9/9] gnu: sdrangel: Add dsdcc support Guillaume Le Vaillant
2021-05-04 16:39 ` Leo Famulari
2021-05-04 20:02 ` Leo Famulari
2021-05-04 21:48 ` Guillaume Le Vaillant
2021-05-04 20:00 ` [bug#48217] [PATCH 1/9] gnu: Add csdr Leo Famulari
2021-05-04 21:34 ` Guillaume Le Vaillant
2021-05-04 16:38 ` Leo Famulari [this message]
2021-05-05 8:48 ` [bug#48217] [PATCH v2 " Guillaume Le Vaillant
2021-05-05 8:48 ` [bug#48217] [PATCH v2 2/9] gnu: Add serialdv Guillaume Le Vaillant
2021-05-05 8:48 ` [bug#48217] [PATCH v2 3/9] gnu: aptdec: Update to 1.7-1.5f91799 Guillaume Le Vaillant
2021-05-05 8:48 ` [bug#48217] [PATCH v2 4/9] gnu: Add cm256cc Guillaume Le Vaillant
2021-05-05 11:22 ` Maxime Devos
2021-05-05 13:37 ` Guillaume Le Vaillant
2021-05-05 8:48 ` [bug#48217] [PATCH v2 5/9] gnu: Add libdab Guillaume Le Vaillant
2021-05-05 8:48 ` [bug#48217] [PATCH v2 6/9] gnu: Add sgp4 Guillaume Le Vaillant
2021-05-05 8:48 ` [bug#48217] [PATCH v2 7/9] gnu: Add mbelib Guillaume Le Vaillant
2021-05-05 8:48 ` [bug#48217] [PATCH v2 8/9] gnu: Add dsdcc Guillaume Le Vaillant
2021-05-05 8:48 ` [bug#48217] [PATCH v2 9/9] gnu: Add sdrangel Guillaume Le Vaillant
2021-05-07 16:48 ` bug#48217: [PATCH 0/9] " Guillaume Le Vaillant
2021-05-08 2:32 ` [bug#48217] " Leo Famulari
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=YJF4hg8wm9yC+LKI@jasmine.lan \
--to=leo@famulari.name \
--cc=48217@debbugs.gnu.org \
--cc=glv@posteo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.