getsolus / getsolus/packages

Install license files for all packages

Open
#7,294 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Priority: Normal
Dominant language
Python
Stars
141
Forks
146
Avg merge
11h 7m
Merged PRs (30d)
407

Description

In the past, packagers were recommended against installing license files for individual packages. It even went so far as to ask people to remove these files if they were shipped by the build system. This is Really Bad, because it means we are in violation of most if not all open source licenses! We MUST install these files in packages.

Guidance on fixing

As of version 35.1.0, ypkg has a macro to easily install license files to the correct directory. Use this macro in the install section of packages that don't ship any license files so that the files are installed. Once built, they should be present in the package's /usr/share/licenses/$package/ directory.

Example
install    : |
    %ninja_install

    # Install a single file from the project's source root called LICENSE
    %install_license LICENSE

    # Install multiple license files present in a directory in the project's source root called LICENSES.
    %install_license LICENSES/*

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review package definitions with an install section and identify those that do not ship license files. Read the ypkg 35.1.0 %install_license guidance, add the appropriate macro usage, then build the affected packages and verify license files appear under /usr/share/licenses/$package/.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.