builded .deb shows wrong license informations
See original GitHub issue- Version: 21.2.0
none
- Target: Linux (.deb)
If i double click the .deb on ubuntu the application software opens up and shows informations about this particular .deb file. Under license it shows “proprietary” while my package.json has the following configured:
...
"license": "GPL-3.0",
"build": {
...
Question:
Is that an error in
- my package.json file,
- the Ubuntu Software Center ui or
- really from electron-builder?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:32
Top Results From Across the Web
.deb install has a proprietary license - desktop - Delta.Chat
I recently tried to download the .deb installation off of the ... we use to package deltachat desktop) builded .deb shows wrong license...
Read more >Is there deb packages that display license agreement?
P.S: That a licence needs to be accepted by the user to be valid or that an accepted licence is automatically valid is...
Read more >How to get information about deb package archive?
Getting licensing information:- Most of archive's copyright information is available from /usr/share/doc/<pkgname>/copyright. Example :- $ ...
Read more >License compliance - GitLab Docs
GitLab checks the License Compliance report, compares the licenses between the source and target branches, and shows the information right on the merge ......
Read more >Visual Studio Code Frequently Asked Questions
Why does Visual Studio Code have a different license than the vscode GitHub repository? To learn why Visual Studio Code, the product, has...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@develar even Visual Studio Code, arguably the most popular open source Electron app, builds a
.deb
that indicates a license of proprietary, when it’s actually MIT licensed. As an open source developer yourself I’m sure you can appreciate the desire to have what you have built be labeled properly. Is there any way this issue can get looked at or prioritized?Still relevant.