| Author | SHA1 | Date | |
|---|---|---|---|
6da6ac2505
|
|||
| c5c621366b | |||
| af6de30546 |
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
6da6ac2505
|
conf / scripts: Fix unprivileged "make install"
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 3m33s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m46s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 3m36s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m46s
CI / Packaging test (push) Successful in 0s
Unprivileged "make install" currently returns an error. That looks bad. It actually is not a real problem, because unprivileged "make install" installs files into locations that are good for nothing, in the sense that they don't constitute a meaningful or usable hierarchy of installed files. Debugging / inspecting the install machinery itself is a valid use case, though, and it's easier to explain to the unsuspecting user that unprivileged installation is something akin to shooting range training than why "make install" outright errors out, so fix the error messages. Signed-off-by: Jan Lindemann <jan@janware.com> |
|||
| c5c621366b |
scripts/usr-bin: scripts.mk -> std-targets.mk
jw-pkg is copied into $(TOPDIR)/bin during build, that's wrong. Write a rule precisely targeted at installing /usr/bin/jw-pkg, and cut all the scripts.mk machinery. Also, make jw-pkg a relative link to avoid the respective RPM warning. Signed-off-by: Jan Lindemann <jan@janware.com> |
|||
| af6de30546 |
scripts/usr-bin: Install symlink /usr/bin/jw-pkg
Install a symlink /usr/bin/jw-pkg -> /opt/jw-pkg/bin/jw-pkg.py in order to have jw-pkg in $PATH. Signed-off-by: Jan Lindemann <jan@janware.com> |