beeware / beeware/briefcase

RPM and PKG packages need license information

Open
#1,829 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
3.3k
Forks
549
Avg merge
1d 4h
Merged PRs (30d)
40

Description

### Describe the bug

RPM and PKG packages include a short descriptor for the license, but after #1812 Briefcase will no longer know that (it either has a licence file or a licence text which may or may not be a short descriptor). Consequently, it is always set to "Unknown".

Prior to #1812 briefcase *might* have a way to know the license descriptor, but it is no guarantee that it matches the LICENSE file.

### Steps to reproduce

1. Build an RPM or PKG bundle
2. Look at the spec file
3. Observe that the "License" field is set to "Unknown"

### Expected behavior

A short license descriptor is included in the RPM spec file and the PKGBUILD-file

### Screenshots

_No response_

### Environment

Any environment

### Logs

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by locating the code that generates RPM spec files and PKGBUILD files, then trace how the license value is obtained after #1812. Confirm the generated RPM spec and PKGBUILD contain a short license descriptor rather than "Unknown", and run the relevant packaging tests if present.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.