Re: [PATCH] Makefile: enable DEVELOPER by default

From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>,
	"'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>,
	"'Junio C Hamano'" <gitster@pobox.com>
Cc: 'Duy Nguyen' <pclouds@gmail.com>,
	'Jonathan Nieder' <jrnieder@gmail.com>,
	'Stefan Beller' <sbeller@google.com>,
	'Git Mailing List' <git@vger.kernel.org>,
	git-packagers@googlegroups.com,
	'Han-Wen Nienhuys' <hanwen@google.com>
Subject: Re: [PATCH] Makefile: enable DEVELOPER by default
Date: Sun, 02 Sep 2018 02:31:55 +0530	[thread overview]
Message-ID: <9f7b6b5b0525b0d360423e3416d7baacd4c5a5cc.camel@gmail.com> (raw)
In-Reply-To: <001001d42da7$4a9e6570$dfdb3050$@nexbridge.com>

On Mon, 2018-08-06 at 13:02 -0400, Randall S. Becker wrote:
> 
> Any idea when this is going to be in an official release, and exactly
> what the settings will be for "Not Developer". I assume DEVELOPER=0
> and DEVOPTS=error, which is the current behaviour, correct? I am the
> platform maintainer for HPE NonStop and need to make sure I'm not
> packaging DEV builds to anyone, since I'm the only one doing this for
> the platform. It's another hoop, but hopefully not a bad one. The
> question is the best place to set this, assuming we are using Jenkins
> for our builds, and I'd rather keep the existing config.mak.uname the
> same, since at least it seems stable.

Just a FYI and in case you aren't aware, you could create a
"config.mak" to store your custom configurations. You can be sure it's
used due to the following Makefile part:

...

include config.mak.uname
-include config.mak.autogen
-include config.mak
...

It's just not a hard dependency.

Hope that helps,
Sivaraam