From owner-freebsd-ports@FreeBSD.ORG Fri Jun 17 16:07:39 2011 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67D151065675 for <ports@freebsd.org>; Fri, 17 Jun 2011 16:07:39 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 0B8568FC12 for <ports@freebsd.org>; Fri, 17 Jun 2011 16:07:38 +0000 (UTC) Received: from megatron.madpilot.net (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP id 0FD461830; Fri, 17 Jun 2011 17:49:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received; s=mail; t=1308325791; x= 1310140191; bh=LgweZkYBt1M/19qt/wG3ZFE2cUh3zI5qLQKlktk2xBQ=; b=C lRuudKYRjjitzxLdE8Gcc4l0+9WDNf9u0mn78gEo1GKMfw9GyXdVO8ThSLbxXM/g pf9EYHjC1/FddiWJAR2LPA3VzmA4d7rvKZIZSmbPxqxWtOJp8cxaW9S3IJIUx2mp q6pwfCM1Z5w4Eat/jdNEZtWySH0+8yJXx4zWyW7poc= X-Virus-Scanned: amavisd-new at madpilot.net Received: from megatron.madpilot.net ([127.0.0.1]) by megatron.madpilot.net (megatron.madpilot.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 6i4STkORPmId; Fri, 17 Jun 2011 17:49:51 +0200 (CEST) Received: by megatron.madpilot.net (Postfix, from userid 1000) id 3941D1827; Fri, 17 Jun 2011 17:49:51 +0200 (CEST) Date: Fri, 17 Jun 2011 17:49:51 +0200 From: Guido Falsi <mad@madpilot.net> To: Ruslan Mahmatkhanov <cvs-src@yandex.ru> Message-ID: <20110617154950.GC37006@megatron.madpilot.net> References: <4DFB6148.1000407@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DFB6148.1000407@yandex.ru> X-Operating-System: FreeBSD 8.2-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Ports Mailing List <ports@freebsd.org> Subject: Re: tinderbox question X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports> List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 17 Jun 2011 16:07:39 -0000 On Fri, Jun 17, 2011 at 06:14:32PM +0400, Ruslan Mahmatkhanov wrote: > Good day. > > How can i `inject` updated (or new) port into tinderbox Build to > test it for correctness? I mean i have not any troubles to build any > existing port, but what should i do to place updated or new port > into the tinderbox portstree? I'm using a personal strategy. I have two portstrees in my tinderbox. One is the official tree another one is my tree, which I update "by hand" It really is a freebsd ports tree managed using monotone, so I can add my patches and also easily merge snapshots from the offical ports tree. I choose monotone because after test with various RCS it came out as faster and easier for this use case than others. Obviously YMMV. I then have a set of builds referring the official tree to build official packages for my machines and another set of builds referring my own ports tree for testing packages. The builds connected to the test tree also have less ports to build than the official ones because there I build just what I maintain or make patches for. This method also has the advantage that you can have different configs, options and so on for the ports in the different builds. Hope this helps. -- Guido Falsi <mad@madpilot.net>