[Midnightbsd-mports] DEVELOPER options appear to be broken/incomplete

[Lucas Holt]

On 9/24/21 2:22 PM, Chris wrote:
> Well I ported a couple of additional ports -- ahem... Mports
> as well as 3 additional depends that one of them had to
> MidnightBSD. I would have submitted them yesterday. But went
> to install my favorite console editor: editors/vim. Only to
> find it was broken. So in an effort to expedite fixing it; I
> set DEVELOPER=true in make.conf(5). Which revealed that that
> /too/ was broken/incomplete -- /mports/Mk/Scripts/sed_checked.sh
> was missing. To expedite the matter I simply copied over the
> file from one of my FreeBSD boxes. I can't know if it's the
> right version of course. But it silenced the make error. :-/
> Anyway. Thought I'd bring it up in case anyone might have
> some additional pointers/information. So I can clear up the
> anemic DEVELOPER option(s).


Normally, we use MPORT_MAINTAINER_MODE=YES in /etc/make.conf to enable 
developer related settings.  There are some things that were brought in 
over time from FreeBSD ports with respect to the DEVELOPER option and it 
might be nice to get those working all the way.

The primary benefit of MPORT_MAINTAINER_MODE is that it enables 
additional checks for plists. it will tell you if things are installed 
outside of the fake directory in many cases, and also if things are 
missing. fake is pretty similar to FreeBSD stage except that it predates 
it and there are a few differences in behavior. Most notably the 
do-install, post-install targets get DESTDIR prepended to PREFIX but the 
newer options specific ones do not. You can get the real prefix with 
TRUE_PREFIX and STAGEDIR becomes FAKE_DESTDIR.

The only other difference is an annoying OPTIONS bug I haven't tracked 
down where it can prompt you for make config over and over.  I suspect 
it's either included at the wrong time or that it's not saving the 
options file properly due to a path issue. This is mostly noticeable on 
python ports that use options.