Dennis Clarke writes: > The other issue that arises here is that a patch has a dependency tree also. > If I have a package that requires only a few small changes then a patch > makes sense. If I then make another release with a few more changes then we > have yet another patch. However these patches now depend on previous > editions of the patch. In order to get an upto date Apache we need the patch > "today" to include all the patch changes from previous patches in a > summative way ( if there is such a term ) and we need to be able to go from > a five year old Apache to todays Apache in one fell swoop with the grand > unified patch.
Right; you would need to deal with the complex and undocumented issues related to patching. I would not recommend attempting to deliver these things by way of patches. The original question, though was about whether Sun uses patches to avoid the package remove/install design pattern, and that's not quite the case. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
