In article <9406100132.AA17502@rrzc1.rz.uni-regensburg.de> Hubert Feyrer <Hubert.Feyrer@rz.uni-regensburg.de> writes:
> 
> Erm, could you please repost those quidelines here?

Here's the basic procedure I use, based on a current-users message from
Mark Weaver.  You have to modify it to deal with any changes that
require special care (like syscall changes, or the sh bug, etc).
Basicly, use common sense and watch current-users (especially daily CVS
update messages) for things that might need special attention.

Clean tree
Build/Install src/usr.bin/make; make clean
Build/install other build tools that have changed; make clean
Install src/share/mk
cd /usr/src
rm -rf obj if it exists; mkdir obj
make -k obj
make -k depend
Build/Install src/usr.sbin/config.new; make clean
Install src/include
Build src/sys/lib
Build/Install/Reboot kernel (after make clean)
Build/Install src/lib
Build/Install src/gnu/lib/libmalloc
Build/Install src/gnu/usr.bin/gcc2/libgcc
Build/Install src/gnu/usr.bin/ld
Rebuild/Install libs
Build everything
Install everything


-- 
Ty Sarna	     "It pays to be obvious, especially if you have a 
tsarna@endicor.com    reputation for subtlety" -- Salvor Hardin

------------------------------------------------------------------------------