From: Phicem <Phicem@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: rtl8192eu-dkms-20221031
Date: Sun, 06 Nov 2022 19:56:39 +0100 [thread overview]
Message-ID: <20221106185639.K9HFeURv3jocpyaeGQHsXhhMzYib1w-bZcWWmwduHGc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30121@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3005 bytes --]
New review comment by Phicem on void-packages repository
https://github.com/void-linux/void-packages/pull/30121#discussion_r1014876537
Comment:
I think it's not as bad as it looks.
The comment that you quoted above refers to the original code (first commit of the repo), which is downloadable from DLINK website. I tried to get into depth into what was released under GPL and what was not.
### In the original code
- There is no general license information
- the Makefile (and some other trivial config files and trivial scripts) have no author and no license information
- most of the 333 source files (.h and .c) have license information (GPL2), except 39 files
- there are 16 .c files without license information:
- 2 files have no author information (`./core/rtw_wapi.c` and `./core/rtw_wapi_sms4.c`)
- 12 files have an author name ("Cosa") (`./hal/OUTSRC-BTCoexist/HalBtc*`)
- 2 files are Copyright Realtek (`./hal/rtl8192e/Hal8192EPwrSeq.c` and `./os_dep/linux/wifi_regd.c`)
- there are 23 header files without license information.
### In current code
Recent versions of the repo (which would be what would be packaged here) have even less license-less files:
- the Makefile (and some other trivial config files and trivial scripts) still have no author or license information
- all but 4 of the 512 source files (.h and .c) have license information (GPLv2)
- there is 1 .c file without license information:
- this file is `./hal/btc/halbtc8192e2ant.c`
- this file mentions an author name ("Cosa") in the history section
- this file exists in a different form in many other repositories, including the linux kernel itself, with GPL license. What I mean by 'different form' is that the code has undergone many changes, but the mentioned author is the same. See for instance: [in the linux kernel](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/realtek/rtlwifi/btcoexist/halbtc8192e2ant.c?h=v6.1-rc3&id=f1d2b4d338bf090296f67830025228872fd52513)
- there are 3 header files without author or license information
- one is a trivial file `./include/rtw_version.h`
- the second one is `./hal/btc/halbtc8192e2ant.h` and also exists in the linux kernel in another form (many changes in the code but same base)
- the thirst one is `./hal/phydm/phydm_regtable.h` but is a long list of trivial `#define`
### Conclusion
Apart from the makefile and some trivial scripts and headers, there are only two files that are not explicitely GPLed : `./hal/btc/halbtc8192e2ant.c` and its corresponding header. The fact that modified versions of these files can be found as GPL-released files tends to reassure me, but still, I have no proof that the exact files we use are GPL. Moreover, I have no license information at all about the makefile.
If we say that this is a problem, could we put the package in the `nonfree` repository, with a license field like `license="GPL-2.0-only, custom:unknown"`?
next prev parent reply other threads:[~2022-11-06 18:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 14:26 [PR PATCH] New package: rtl8192eu-dkms-20210111 Phicem
2022-04-16 12:58 ` [PR PATCH] [Updated] " Phicem
2022-04-16 13:01 ` Phicem
2022-07-16 2:13 ` New package: rtl8192eu-dkms-20220406 github-actions
2022-07-27 20:25 ` Phicem
2022-10-27 2:13 ` github-actions
2022-11-05 17:27 ` [PR PATCH] [Updated] " Phicem
2022-11-05 17:30 ` Phicem
2022-11-05 18:05 ` [PR REVIEW] New package: rtl8192eu-dkms-20221031 paper42
2022-11-05 18:05 ` paper42
2022-11-05 18:05 ` paper42
2022-11-05 18:05 ` paper42
2022-11-06 18:56 ` Phicem [this message]
2022-11-06 19:09 ` Phicem
2022-11-20 0:01 ` classabbyamp
2023-02-18 1:59 ` github-actions
2023-02-18 20:05 ` [PR PATCH] [Updated] " Phicem
2023-02-18 20:08 ` [PR REVIEW] " Phicem
2023-02-18 20:10 ` Phicem
2023-05-21 1:56 ` New package: rtl8192eu-dkms-2022.12.29 github-actions
2023-06-04 2:12 ` [PR PATCH] [Closed]: " github-actions
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=20221106185639.K9HFeURv3jocpyaeGQHsXhhMzYib1w-bZcWWmwduHGc@z \
--to=phicem@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).