'\" t
.\"     Title: pkgctl-license-setup
.\"    Author: [see the "AUTHOR(S)" section]
.\" Generator: Asciidoctor 2.0.23
.\"      Date: 2025-07-29
.\"    Manual: \ \&
.\"    Source: \ \&
.\"  Language: English
.\"
.TH "PKGCTL\-LICENSE\-SETUP" "1" "2025-07-29" "\ \&" "\ \&"
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.ss \n[.ss] 0
.nh
.ad l
.de URL
\fI\\$2\fP <\\$1>\\$3
..
.als MTO URL
.if \n[.g] \{\
.  mso www.tmac
.  am URL
.    ad l
.  .
.  am MTO
.    ad l
.  .
.  LINKSTYLE blue R < >
.\}
.SH "NAME"
pkgctl-license-setup \- Automatically detect and setup a basic REUSE configuration
.SH "SYNOPSIS"
.sp
pkgctl license setup [OPTIONS] [PKGBASE...]
.SH "DESCRIPTION"
.sp
This subcommand automates the creation of the Arch Linux 0BSD package license
file as well as a basic reuse(1) configuration by applying simple heuristics.
It comes in especially handy when initially setting up licensing for a package
without the need to manually write a \f(CRREUSE.toml\fP file.
.sp
If any \f(CR.patch\fP files are detected and the PKGBUILD(5) has only a single entry
in the \f(CRlicense=()\fP array, this subcommand assumes the patches are licensed
under that license and generates annotations for them.
.sp
In case there are no patches, no additional annotations are generated.
.sp
Manual annotations are necessary in case the subcommand can\(cqt generate a
configuration that accounts for all files. In this case, \f(CRreuse lint\fP will fail
with a descriptive error of which files are missing an annotation.
.sp
If no \f(CRPKGBASE\fP is specified, the command defaults to using the current working
directory.
.SH "OPTIONS"
.sp
\fB\-f, \-\-force\fP
.RS 4
Overwrite existing reuse(1) configuration
.RE
.sp
\fB\-\-no\-check\fP
.RS 4
Do not run pkgctl\-license\-check(1) after setup
.RE
.sp
\fB\-h, \-\-help\fP
.RS 4
Show a help text
.RE
.SH "SEE ALSO"
.sp
pkgctl\-license(1)
pkgctl\-license\-check(1)
reuse(1)
PKGBUILD(5)
.SH "HOMEPAGE"
.sp
\fI\c
.URL "https://gitlab.archlinux.org/archlinux/devtools" "" "\fP"
.sp
Please report bugs and feature requests in the issue tracker. Please do your best to provide a reproducible test case for bugs.