matthewa@materna.nl writes:

>That made me want to 'cd /usr/pkgsrc/netbsd/syssrc && make', so I could

The most prominent problem is that pkgsrc is a batch oriented system
whereas building a new kernel is an interactive process (you normally
have to modify the config file, for example.)  Also, where should
it build the stuff?  *pkgsrc*syssrc/work?  /usr/src/sys?  /usr3/src/sys?
/import/nbsd/1.5/src/sys?  People often have different trees, which
would get clobbered if they were expected to be at the same situation.
If the syssrc were a dependency, and the depending package absolutely
required a new kernel, would pkgsrc then have to reboot the system
after replacing the running kernel with a new GENERIC one so that
installation could be finished, probably in batch operation, with
the system administrator offline when he didn't even know there
was a dependency on the kernel?  Quite a lot of problems to look
into.  One also has to make sure then, that a future situation in
which pkgsrc would be _required_ to build system (and userland)
does not occur.

--mkb