You can just use "--target host-tuple" in prepare(). There's two licenses to deal with, one for the software you're packaging(in this case MIT, I didn't verify), and one for the packaging scripts you're creating(0BSD).
> Is this cause for concern? "Missing repo package/target not found" just means the package does not exist in the repo you're building it for, which will always be the case for this package. Martin On Sat, Jan 24, 2026 at 1:09 PM Garrett <[email protected]> wrote: > > Howdy y'all - > > I found a neat project called > [RMPC-Auto-Theme](https://github.com/animegolem/RMPC-Auto-Theme) that > generates rmpc themes from album art, and to build up my portfolio, > I figured I'd try adding it to the AUR. > I've created a [pkgbase](https://dl.depot.4d2.org/CClGAodB6ZtU.tar.xz) that > I'd like to push - > I bootstrapped from a PKGBUILD make by `cargo-pkgbuild`, > have been using an install for the day from a local `makepkg -si`, and > got it to build in a `pkgctl build` with no errors from `namcap` - > but I'd like a sanity check on licensing and reproducibility first. > > * I didn't understand the `REUSE.toml` business from `pkgctl license setup` > and `pkgctl license check` so, rather than use Arch's `0BSD` license, > just copied the MIT license from upstream - is this valid? > * There was some strangeness with the `checkpkg`: > ``` > Checking PKGBUILD > Checking rmpc-auto-theme-git-debug-r22.e0f6399-1-x86_64.pkg.tar.zst > rmpc-auto-theme-git-debug W: Directory (usr/src/debug/rmpc-auto-theme-git) > is empty > Checking rmpc-auto-theme-git-r22.e0f6399-1-x86_64.pkg.tar.zst > ==> Running checkpkg > error: target not found: rmpc-auto-theme-git > ==> WARNING: Skipped checkpkg due to missing repo packages > ==> Generating .SRCINFO...done > ``` > Is this cause for concern? > * Otherwise, does everything read sanely? > > If everything looks good, I'll push to the AUR and also request from upstream > that they add the AUR link to their repo. > > Cheers, appreciate y'all's input! > > Garrett
