On Tue, 25 Apr 2000, Jim Bloom wrote:

> The RCS info stored in the binaries is insufficient for this purpose.  There is
> no record of the versions of all included files.  Changes to constants and/or
> macros would not be identifiable.

Yes, you're right, I'm afraid. This could theoretically be solved by
adding an ELF section at the build stage, containing the RCS versions from
files reported by 'make depend'. But at this point the things get ugly and
complicated very quickly... :-(

The simple approach could be as follows: start with the official version
of the RELEASE (which takes care of having one common version, with known
MD5 cksums). The patchkits would contain only the whole files, not diffs.
The patch installer would have to examine the target files before doing
anything, and if the MD5 checksums (relative to the last patchkit) don't
match - present a choice, in a way similar to mergemaster.

This way, we can push the responsibility for tracking dependencies to the
user... :-/

Andrzej Bialecki

//  <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com)
// -------------------------------------------------------------------
// ------ FreeBSD: The Power to Serve. http://www.freebsd.org --------
// --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ----

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to