From owner-freebsd-ports@FreeBSD.ORG Sun Mar 6 15:42:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FEF9106566B for ; Sun, 6 Mar 2011 15:42:47 +0000 (UTC) (envelope-from magik@roorback.net) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id A2DF78FC1B for ; Sun, 6 Mar 2011 15:42:46 +0000 (UTC) Received: by eyg7 with SMTP id 7so1210514eyg.13 for ; Sun, 06 Mar 2011 07:42:45 -0800 (PST) Received: by 10.213.28.69 with SMTP id l5mr954592ebc.77.1299426165216; Sun, 06 Mar 2011 07:42:45 -0800 (PST) Received: from silver.nine (89-72-104-219.dynamic.chello.pl [89.72.104.219]) by mx.google.com with ESMTPS id t5sm1256974eeh.8.2011.03.06.07.42.43 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 Mar 2011 07:42:44 -0800 (PST) Message-ID: <4D73AB72.5000405@roorback.net> Date: Sun, 06 Mar 2011 16:42:42 +0100 From: Grzegorz Blach User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110305 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: FreeBSD needs fresh Blood! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2011 15:42:47 -0000 I read last post Martin Wilke's blog called "FreeBSD needs fresh Blood!" First of all, I think it's difficult to testing ports. I'm using testing release of VirtualBox, but for build this port I must download patches, apply its on my own tree and merge its with official ports using portshaker. It's possible to build testing ports outside tree, but I must build every port separately, since `Make` don't known how to track dependencies. Another possibility is replace ports in disk, but after upgrade tree eg. with portsnap I lose my changes, and portmaster want to rebuild these ports to stable release. If testing will be simpler, I think more people will do this. Maybe we must create two trees, eg: ports-stable and ports-current First we publish changes to current tree and after week or two without pr, we publish updates to stable tree too. Merging trees is another huge problem. Portshaker do this very well, but after merge I must rebuild INDEX file, which takes long time. This should be faster or even shouldn't be required (hard to do).