Not to start off another thread on make.conf options such as NOUUCP, NOYP,
NO<don't_want_it> a somewhat cryptic:
Cy Schubert <[EMAIL PROTECTED]> writes:
> A previous posting of mine conveyed the idea of variables like
> NOUUCP=true, NOSENDMAIL, NONAMED, NOYP, SUID_BINARIES_root='/usr/bin/su
> ...' etc., in make.conf. Wouldn't this work?
Read /usr/share/mk/bsd.subdir.mk.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
Looking around one finds:
# +++ variables +++
#
# DISTRIBUTION Name of distribution. [bin]
#
# SUBDIR A list of subdirectories that should be built as well.
# Each of the targets will execute the same target in the
# subdirectories.
#
# SUBDIR_CHANGE A directory-tree that contains overrides for
# corresponding build subdirs.
# Each override is a file containing one subdirname per line:
# 'subdirlist' is a pure override
# 'subdirdrop' drops directories from the build
# 'subdiradd' adds directories to the build
--
.if defined(SUBDIR_CHANGE) && !empty(SUBDIR_CHANGE) && \
exists(${SUBDIR_CHANGE}/${DIRPRFX}/subdirlist)
SUBDIR!=cat ${SUBDIR_CHANGE}/${DIRPRFX}/subdirlist
.endif
.if defined(SUBDIR_CHANGE) && !empty(SUBDIR_CHANGE) && \
exists(${SUBDIR_CHANGE}/${DIRPRFX}/subdirlist)
_SUBDIR_EXTRA!=cat ${SUBDIR_CHANGE}/${DIRPRFX}/subdiradd
.endif
_SUBDIRUSE: .USE
@for entry in ${SUBDIR} ${_SUBDIR_EXTRA}; do \
(if ! (test -f ${SUBDIR_CHANGE}/${DIRPRFX}/subdirdrop && \
grep -w $${entry} \
${SUBDIR_CHANGE}/${DIRPRFX}/subdirdrop \
> /dev/null); then \
if test -d ${.CURDIR}/$${entry}.${MACHINE}; then \
${ECHODIR} \
"===> ${DIRPRFX}$${entry}.${MACHINE}"; \
edir=$${entry}.${MACHINE}; \
cd ${.CURDIR}/$${edir}; \
else \
${ECHODIR} "===> ${DIRPRFX}$$entry"; \
edir=$${entry}; \
cd ${.CURDIR}/$${edir}; \
fi; \
${MAKE} ${.TARGET:realinstall=install} \
SUBDIR_CHANGE=${SUBDIR_CHANGE} \
DIRPRFX=${DIRPRFX}$$edir/; \
fi; \
); \
done
In /usr/src on could then have:
./gnu/subdirdrop
./libexec/subdirdrop
./bin/subdirdrop
./sbin/subdirdrop
./usr.bin/subdirdrop
./usr.sbin/subdirdrop
./subdirdrop
These files contain directories (corresponding to binaries) that should be
skipped over when building/installing.
Do the files require a relative path (doesn't appear so in bsd.subdir.mk)?
What function does the variable SUBDIR_CHANGE have, as well as the value of
it?
Feel I'm missing something (besides sleep). Might be that I would need and
environment variable like so:
SUBDIR_CHANGE= \
gnu \
libexec \
bin \
sbin \
usr.bin \
usr.sbin
One could just edit the makefiles, but then they would be clobbered with
every CVSup or need to merge changes. Rather have a mechanism that is
independant, doesn't get clobbered, and isn't just an editing kludge.
Could be I end up shooting myself in the foot by removing too much, but
another build would fix that easy enough.
Jeff Mountin - [EMAIL PROTECTED]
Systems/Network Administrator
FreeBSD - the power to serve
'86 Yamaha MaxiumX (not FBSD powered)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
