Yes, that would be helpful.  Some which I recall offhand that are not
MAKE_JOBS_SAFE:

devel/nspr
lang/spidermonkey
textproc/glimpse
lang/f2c
audio/libsndfile
security/libgpg-error
textproc/asciidoc
graphics/netpbm
audio/nas
maybe gnome-user-docs and/or evolution-data-server
I think some other gnome packages

I used to have a huge list but deleted it by accident a few weeks ago.
 To create a centralized list, what you can do is this:

edit the line in mk/build/build.mk which checks MAKE_JOBS_SAFE (it's
not too far down from the top).  Add something like:

|| (defined(MAKE_JOBS_OVERRIDE && (MAKE_JOBS_OVERRIDE:M${PKGBASE})) to
the first line in the block of conditionals.  Then define
MAKE_JOBS_OVERRIDE as a list of packages (PKGBASE only, obviously) in
mk.conf which you know to be unsafe.  This is easier, IMHO, than
editing tons of makefiles and allows one to keep track of "usafe"
packages more easily.

Hope this helps,

--Blair

-- 
Support WFMU-FM: free-form radio for the masses!
<http://www.wfmu.org/>

"The frivolity and boredom which unsettle the established order, the
vague foreboding of something unknown, these are the heralds of
approaching change.  The gradual crumbling that left unaltered the
face of the whole is cut short by a sunburst which, in one flash,
illuminates the features of the new world."  --G.W.F. Hegel,
_Phenomenology of Spirit_ 5:11