install path not follow FHS standard

[GoogleCodeExporter]

What steps will reproduce the problem?
1. make DESTDIR="package_dir" install
2. The files will install to non standard directories.


What is the expected output? What do you see instead?

man page: should install to usr/share/man/man3
sample shell: should install to 

What version of the product are you using? On what operating system?


Please provide any additional information below.

I use 'namcap' utility for checking the package path, here is the result

sockperf-svn W: Potential non-FHS man page 
(usr/share/sockperf/man/man3/sockperf.3) found.
sockperf-svn W: File (usr/etc/) exists in a non-standard directory.
sockperf-svn W: File (usr/etc/sockperf/) exists in a non-standard directory.
sockperf-svn W: File (usr/etc/sockperf/vma_perf_envelope.sh) exists in a 
non-standard directory.
sockperf-svn W: File (usr/etc/sockperf/avner-master-test.sh) exists in a 
non-standard directory.
sockperf-svn W: File (usr/etc/sockperf/avner-test.sh) exists in a non-standard 
directory.
sockperf-svn W: File (usr/etc/sockperf/avner-test-orig) exists in a 
non-standard directory.
sockperf-svn W: File (usr/etc/sockperf/vma_multiplexers_test.sh) exists in a 
non-standard directory.
sockperf-svn W: File (usr/etc/sockperf/avner-analyze.awk) exists in a 
non-standard directory.

Original issue reported on code.google.com by [email protected] on 8 Dec 2014 at 7:59

[GoogleCodeExporter]

Thanks for reporting.
I am not sure when we'll reach handling that internally.  Feel free to provide 
a patch and we'll integrate it.

Original comment by [email protected] on 8 Dec 2014 at 8:33

• Added labels: Pjm-Visited
• Removed labels: Pjm-New