>Number:         29885
>Category:       pkg
>Synopsis:       mk-files package is missing files
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 04 23:23:00 +0000 2005
>Originator:     reed@reedmedia.net
>Release:        NetBSD 1.6.2_STABLE
>Organization:
http://bsd.reedmedia.net/
>Environment:
	
	
System: NetBSD rainier.reedmedia.net 1.6.2_STABLE NetBSD 1.6.2_STABLE (MYKERNEL) #1: Tue Jun 1 12:16:43 PDT 2004 reed@rainier.reedmedia.net:/usr/src/sys/arch/i386/compile/MYKERNEL i386
Architecture: i386
Machine: i386
>Description:
If you build a mk-files package and then use it on another system with
bmake you may get errors like:

  bmake: no system rules (sys.mk).

I have had this problem for a couple years.

I don't understand why the package doesn't install all the files
when they are required.

My workaround is to manually copy the files from one system to another
which defeats the purpose of having an easy-to-use package.

(Another mk-files PR is pkg/26603.)

>How-To-Repeat:
Make an mk-files package and use it on another system with bmake
without any sys.mk related files.
>Fix:
Either always install and register (in PLIST) all the files.

Or add an option so I can choose to install and register (in PLIST)
all the files.

>Unformatted: