Subject: Re: pkg/28392 pkgsrc should use a variable name other than MAKEFILE
To: None <pkg-manager@netbsd.org, gnats-admin@netbsd.org,>
From: OBATA Akio <obata@lins.jp>
List: pkgsrc-bugs
Date: 04/15/2006 13:30:07
The following reply was made to PR pkg/28392; it has been noted by GNATS.

From: OBATA Akio <obata@lins.jp>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/28392 pkgsrc should use a variable name other than MAKEFILE
Date: Sat, 15 Apr 2006 22:29:23 +0900

 It's for this reason that Interix's bmake don't set MAKEFILE now.
 This may break to build packages using MAKEFILE as original purpose.
 
 Interix's NFS problem is when open a file, became case
 insensiveite for a while about that file.
 `bmake' try to open `makefile' since then `Makefile' if `-f' option is
 not specified.
 It's for this NFS problem and bmake's specification that
 first `bmake' in pkgsrc directry, open `Makefile' then MAKEFILE==Makefile
 but subsequent next `bmake` open `makefile' then MAKEFILE==makefile.
 Prior to install phase, it's may OK if having sufficient interval time.
 But in install phase, calling oneself like this:
    ${_PKG_SILENT}${_PKG_DEBUG}cd ${.CURDIR} && ${MAKE} ${MAKEFLAGS} do-install
 So, in `do-install', MAKEFILE==makefile.
 
 `MAKEFILE' should not use as makafile in the pacages's build directory.
 
 Make related values is now:
 MAKE_ENV
 MAKE_PROGRAM
 MAKE_FLAGS
 
 Why don't we change from `MAKEFILE' to `MAKE_FILE'?
 
 If need makefile dependin on the phase, now there are some variables:
 BUILD_MAKE_FLAGS
 TEST_MAKE_FLAGS
 INSTALL_MAKE_FLAGS
 
 So, shall we use:
 BUILD_MAKE_FILE
 TEST_MAKE_FILE
 INSTALL_MAKE_FILE