From owner-freebsd-hackers@FreeBSD.ORG  Thu Jan 19 07:00:49 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 581C7106564A
	for <freebsd-hackers@freebsd.org>; Thu, 19 Jan 2012 07:00:49 +0000 (UTC)
	(envelope-from vermaden@interia.pl)
Received: from smtpo.poczta.interia.pl (smtpo.poczta.interia.pl
	[217.74.65.207])
	by mx1.freebsd.org (Postfix) with ESMTP id 0B3EA8FC15
	for <freebsd-hackers@freebsd.org>; Thu, 19 Jan 2012 07:00:48 +0000 (UTC)
Date: Thu, 19 Jan 2012 08:00:48 +0100
From: vermaden <vermaden@interia.pl>
To: freebsd-hackers@freebsd.org
X-Mailer: interia.pl/pf09
In-Reply-To: <hspnzfadjueiouakcbby@isuh>
References: <iwnlzjkfomlarmtwnxdp@dbyr> <hspnzfadjueiouakcbby@isuh>
X-Originating-IP: 194.0.181.128
Message-Id: <jcmlctthomijzcvyfyst@aytd>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl;
	s=biztos; t=1326956447;
	bh=fIl7gY0VkmEbxOtJFUx3F4RRj/yGKcSgsdU9oeED6b4=;
	h=Date:From:Subject:To:X-Mailer:In-Reply-To:References:
	X-Originating-IP:Message-Id:MIME-Version:Content-Type:
	Content-Transfer-Encoding;
	b=PT5BziOwt324f1hRJ+WPLm+7OsrmsgwrUzPVyNs1KsekvE6MYNkUQDU97l3XLjLj2
	HUj8Un+lyuhISuQ4mrLoffeT8icJpq1XYBhY4T2Yo3ASiYh7mkP9DXyV+78nVyuR5q
	buAUtgsk6j/iyWeUETifO3yAVGUhwcx1lQ0BAncE=
Subject: FreeBSD has serious problems with focus, longevity, and lifecycle
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 07:00:49 -0000

A simple sollution (at least for a start), for backporting
various bugfixes from STABLE to RELEASE.

Currently we have /var/db/pkg 'db' for installed ports,
where an installed port is like /var/db/pkg/portname-1.0
lets provide another one, /var/db/patch, a separated
'repository' that would list installed patches/backports
from STABLE to RELEASE, for example:

# pkg_info
aspell-0.60.6.1     Spelling checker with better suggestion logic than
ispell
automake-1.11.1     GNU Standards-compliant Makefile generator (1.11)
binutils-2.22       GNU binary tools
bison-2.4.3,1       A parser generator from FSF, (mostly) compatible with
Yacc
blogbench-1.1       Performance Test of Filesystem I/O
(...)

# patch_into
network-intel_drivers-em-1.0   Some fancy descritpion here
usb-hubfix-3.0                 Some other fancy descritpion

Similar for patch_add(1)/patch_delete(1) etc.

LOGIC/THEORY:

Adding a PATCH network-intel_drivers-em-1.0 would first move all
files that will be overwritten to /var/db/patch/files, for example
/boot/kernel/if_em.ko to
/var/db/patch/files/network-intel_drivers-em-1.0/boot/kernel/if_em.ko
and then install the new backported/updatet files into the base system
or should I say RELEASE.

The only other thing needed to do is to make freebsd-update AWARE of
the files that are under /var/db/patch/files/*/ to omit them when
checking the checksums for updating process.

I will not write that as I only know basics of C programming
and creating this in SH and then porting it to C seems useless
efort to me.

Regards,
vermaden