From owner-freebsd-current Tue Apr 25 12: 4:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 6742B37BD4A for ; Tue, 25 Apr 2000 12:04:25 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA40198; Tue, 25 Apr 2000 15:04:18 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Apr 2000 15:04:18 -0400 (EDT) From: Garrett Wollman Message-Id: <200004251904.PAA40198@khavrinen.lcs.mit.edu> To: wc.bulte@chello.nl Cc: Garrett Wollman , Richard Wackerbarth , freebsd-current@FreeBSD.ORG Subject: Re: Patchkits: Was :Re: SMP changes and breaking kld object module compatibility In-Reply-To: <20000425210017.A1430@yedi.wbnet> References: <39056A21.C58ED54A@originative.co.uk> <20000425194233.A816@yedi.wbnet> <00042513002803.32593@nomad.dataplex.net> <20000425201600.A1134@yedi.wbnet> <200004251850.OAA40162@khavrinen.lcs.mit.edu> <20000425210017.A1430@yedi.wbnet> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I love binary answers :-) Which brings me to my original point: it looks > like you can only do binary patches relative to a -release. Unless > you want to blindly patch and hope for the best. Rather unlikely. I think you are right. Doing so would still require resolving the full dependency graph, so that programs affected by a library change could all be identified. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message