Page MenuHomeFreeBSD

PROG_OVERRIDE_VARS should override default values
ClosedPublic

Authored by ngie on Mar 29 2019, 7:01 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 13 2024, 7:33 PM
Unknown Object (File)
Mar 13 2024, 7:33 PM
Unknown Object (File)
Mar 13 2024, 7:33 PM
Unknown Object (File)
Mar 10 2024, 1:41 PM
Unknown Object (File)
Feb 7 2024, 6:34 PM
Unknown Object (File)
Jan 3 2024, 12:34 PM
Unknown Object (File)
Jan 3 2024, 12:34 PM
Unknown Object (File)
Jan 3 2024, 12:21 PM
Subscribers

Details

Summary

The behavior prior to this change would not override default values if set in
bsd.own.mk. For example: BINMODE defaults to 0555. If someone wanted to set
the BINMODE to NOBINMODE (0444) for prog, for example, like
BINMODE.prog= ${NOBINMODE}, bsd.progs.mk would not honor the per-prog
setting.

This change unbreaks variables defined in PROG_OVERRIDE_VARS which have
defaults set before bsd.progs.mk is included.

MFC after: 1 momth

Test Plan

capsicum-test, which relies on a program that is installed with NOBINMODE and
04555 (sticky bit set).

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

So the problem is that while overriding BINMODE currently works when including bsd.prog.mk, it doesn't work when including bsd.progs.mk?

So the problem is that while overriding BINMODE currently works when including bsd.prog.mk, it doesn't work when including bsd.progs.mk?

... when bsd.own.mk is pulled in beforehand -- that's correct!

Makes sense now. The new commit message is clearer.

This revision is now accepted and ready to land.Mar 29 2019, 8:40 PM
This revision was automatically updated to reflect the committed changes.