I see that mk-files has an install-mk and an auto PLIST generation
for choosing what mk files to install.

My problem:

  -sh-2.05b# bmake
  bmake: no system rules (sys.mk).

A package created on one system and installed to another has:

-sh-2.05b# ls -l share/mk/
total 96
-r--r--r--  1 reed root  4402 May  5 14:38 autodep.mk
-r--r--r--  1 root root   148 Apr  6 21:12 bsd.perl.mk
-r--r--r--  1 reed root  2611 May  5 14:38 dep.mk
-r--r--r--  1 reed root   962 May  5 14:38 doc.mk
-r--r--r--  1 root root  2551 May  5 14:38 dpadd.mk
-r--r--r--  1 root root   670 May  5 14:38 host-target.mk
-r--r--r--  1 reed root   322 May  5 14:38 init.mk
-r--r--r--  1 reed root  2169 May  5 14:38 java.mk
-r--r--r--  1 reed root 14665 May  5 14:38 lib.mk
-r--r--r--  1 reed root  3526 May  5 14:38 man.mk
-r--r--r--  1 reed root   825 May  5 14:38 nls.mk
-r--r--r--  1 reed root  1548 May  5 14:38 obj.mk
-r--r--r--  1 reed root  6886 May  5 14:38 own.mk
-r--r--r--  1 reed root  5249 May  5 14:38 prog.mk
-r--r--r--  1 reed root  2314 May  5 14:38 subdir.mk
-r--r--r--  1 reed root  1596 May  5 14:38 target-flags.mk
-r--r--r--  1 reed root  4025 May  5 14:38 warnings.mk
-r--r--r--  1 reed root   757 May  5 14:38 yacc.mk

The README.1st says:

  The *.sys.mk files should be installed as sys.mk on the appropriate
  machine.

But as you can see above I have nothing to symlink my sys.mk to.

I don't know why I don't have the many per operating system files.

I see a FORCE_SYS_MK. Can we have some option that always enables this to
do a symlink?

Will it break some systems to always install all mk files to /usr/pkg and
to automatically make a new symlink at /usr/pkg/mk/sys.mk ?

Also, can we have the package install the README too?

I will do this coding if you have any suggestions or advice about this
first.

 Jeremy C. Reed

 	  	 	 BSD News, BSD tutorials, BSD links
	  	 	 http://www.bsdnewsletter.com/

p.s. I have had emails about this before, but today it hits me again.