In message <41644E92.9050207@anand.org>, Anand Buddhdev writes:

>
>And anyway, why does "make update" FIRST remove the old package? Would 
>it not make sense to first build the new package(s), and if all the 
>builds succeed, then to proceed with deleting the old packages and 
>replacing them with new ones? That makes for a very small package 
>unavailability window.
>
It's a serious problem; I don't see a great way around it.  "Compile 
first" works for leaf nodes; it doesn't work when there are library 
dependencies involved.  



		--Steve Bellovin, http://www.research.att.com/~smb