We have an open PR on some problems with the new crypto reachover
	format.
		http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=8487

	Does anyone here have any thoughts or comments?
	(please keep gnats-bugs@gnats.netbsd.org in the cc)

> Description:
>         It used to be the case that one could build an `exportable'
>         system, and then build `domestic' separately, layering it on
>         top.  Now, to build both an `exportable' system and the `secr'
>         set, one has to build the entire system twice.  This is a
>         major pain in the arse.
> 
>         Furthermore, Makefiles which silently DTWT if a file or
>         directory isn't present are an absolutely horrible idea in
>         general.
> 
>         It seems that now we have the worst possible combination: no
>         direct crypto integration, *and* a painful and flaky mechanism
>         for handling the unbundled tree.  Yuck.
> 
> Fix:
>         Go back to making cryptosrc separately buildable, or integrate
>         the crypto directly in the main source tree.


		David/absolute