From owner-freebsd-current Sat Mar 9 16:16:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA07551 for current-outgoing; Sat, 9 Mar 1996 16:16:50 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA07545 for ; Sat, 9 Mar 1996 16:16:47 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA30782; Sun, 10 Mar 1996 11:11:37 +1100 Date: Sun, 10 Mar 1996 11:11:37 +1100 From: Bruce Evans Message-Id: <199603100011.LAA30782@godzilla.zeta.org.au> To: current@FreeBSD.org, wosch@cs.tu-berlin.de Subject: Re: *.mk wishes Sender: owner-current@FreeBSD.org X-Loop: owner-current@FreeBSD.ORG Precedence: bulk >bsd.man.mk: >MANGRP, MANOWN, MANMODE, MANDIR already defined >in bsd.own.mk, should deleted >bsd.own.mk: >new variables DOCGRP, DOCOWN, DOCMODE, DOCDIR for documents I agree. It's convenient to have all the ownerships defined in a central place. Definitions of `OWN' variables are also duplicated in: bsd.lib.mk, bsd.port.subdir.mk, bsd.prog.mk, bsd.subdir.mk: BINOWN and some `OWN' variables aren't defined in bsd.own.mk: KMODOWN, LIBOWN. >sys.mk: >MMAP_RO: read only mmap, for programs like grep, groff, look etc. >MMAP_RW: write works (inn) I don't understand this. C macros should be defined in C headers. Don't add any more system macros to sys.mk. bsd.own.mk and (the system macros in) /etc/make.conf shouldn't be included in sys.mk because sys.mk always gets included by default. bsd.own.mk should be included only in the system `mk' files. Bruce