Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#59813 - [namcap] /opt/$pkgname is not considered valid location for ELF files

Attached to Project: Arch Linux
Opened by Alexander Kobel (akobel) - Sunday, 26 August 2018, 12:16 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 30 August 2018, 01:15 GMT
Task Type Bug Report
Category Arch Projects
Status Assigned
Assigned To Kyle Keen (keenerd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

According to the Namcap wiki page, the rule elffile-not-in-allowed-dirs should accept /opt/$pkgname/ as a valid location for ELF files, in accordance with the Linux Filesystem Hierarchy Standard. (From https://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/opt.html: "Generally, all data required to support a package on a system must be present within /opt/'package', including files intended to be copied into /etc/opt/'package' and /var/opt/'package' as well as reserved directories in /opt.")

But currently namcap reports "ELF files outside of a valid path ('opt/')." and does not seem to check for the $pkgname subdirectory.


Additional info:
* package version(s):
extra/namcap 3.2.8-2 (which reports itself as 3.2.7 with `namcap -v`?)


Steps to reproduce:
makepkg and namcap *.pkg.tar* for the attached trivial PKGBUILD (which just copies sed from /usr/bin to /opt/$pkgname/bin)
   PKGBUILD (0.4 KiB)
This task depends upon

Loading...