From owner-freebsd-current Tue Mar 13 4:41:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 46D5937B726 for ; Tue, 13 Mar 2001 04:41:06 -0800 (PST) (envelope-from mb@imp.ch) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f2DCf3S78657 for ; Tue, 13 Mar 2001 13:41:03 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Tue, 13 Mar 2001 13:41:47 +0100 (CET) From: Martin Blapp To: current@freebsd.org Subject: Proposal to mergemaster Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, After 100erts of mergemaster sessions, I'm looking for a way to improve mergemaster. 1st thing, mergemaster displays per default all in changed files. That's ok for the first time, but if you maintain many hosts, this is annoying a lot. There should be an options to display all changed files anyway, so you can watch what has changed. (but off by default) So I have ideas to improve merge-master: 1. Add md5 checksum to the the file-header: ------------------------------------------- Add an md5 checksum in the header of the File, maybe in $FreeBSD$ when the file get's comitted. (The $FreeBSD$ line should be sed'd/grepp'd out to md5 the raw file without checksum.) grep -v "$FreeBSD:" defaults/rc.conf | md5 Example: # $FreeBSD: src/etc/defaults/rc.conf,v 1.53.2.15 2001/01/28 20:57:35 jdp Exp md5="1fff7b9d6f6daa0ea9635873bfd0b7cd" $ Then mergemaster can do a md5 over the config file and look if the file has changed. If so, you get asked to merge or install a newer version. If the md5 checksum is the same, the config file get's updated without asking the user. 2. Have a special database with md5 checksums --------------------------------------------- The advantage here is that we can use this for binarys also, and this allows us to have binary updates for, let's say, security fixes. For old unsupported releases that's a very good thing. The database stores all md5 checksums for every version of a configfile we had (for this branch so it dosn't get to big ?) The database could also be very useful for later usage in the ports- tree (handle make update) Other ideas are welcome Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message