From owner-freebsd-ports@FreeBSD.ORG Sat Dec 13 19:35:59 2008 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 E3D3E1065670 for ; Sat, 13 Dec 2008 19:35:59 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id B7B968FC12 for ; Sat, 13 Dec 2008 19:35:59 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2008269rvf.43 for ; Sat, 13 Dec 2008 11:35:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=2RfxSAv/gvyomAJTqESvJcSP5n211PqDJIGZsy1vx+Q=; b=EJTJHBVA2JRpiKp0sivw1BUQT1YiJ9tS9tQTFkP8rwleZcNrDgpvQ0o5kRlOo6Leqq nKnM54nkE5blfepR4sHTjjA8BbyUVKxFdSBdtVjtT67wNN5oR1vBqsFYDmr6WK8DpUh3 LCbeqty+9vWdyrC9o9ukp6YTHBlXshVzlLt50= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=kw3+IwLtsOypAq/mD3Ruh0G4LgVMqb21GLcpx1pt0Qxn+zk1+N5BS5r9f2n5F6VQ0z QMJvCM3fFlHwRzlq55fwMGI6c55OfPdfkAFQXk0yfmfTlsE2gpgOTJ1k95J9xIocOScY 6dENeh1T1TaurEGdIySpZ2OhyJ0KaH7X9+UsA= Received: by 10.140.142.11 with SMTP id p11mr1733710rvd.276.1229196959457; Sat, 13 Dec 2008 11:35:59 -0800 (PST) Received: by 10.140.158.13 with HTTP; Sat, 13 Dec 2008 11:35:59 -0800 (PST) Message-ID: <7d6fde3d0812131135p5c47fcegd1115b2da2237427@mail.gmail.com> Date: Sat, 13 Dec 2008 11:35:59 -0800 From: "Garrett Cooper" To: freebsd-ports@freebsd.org In-Reply-To: <20081213103348.GA80526@blogreen.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20081213103348.GA80526@blogreen.org> Subject: Re: Maintaining meta-data for patches 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: Sat, 13 Dec 2008 19:36:00 -0000 On Sat, Dec 13, 2008 at 2:33 AM, Romain Tarti=E8re wr= ote: > Hi! > > As a port maintainer, you sometimes have to provide patches in your > ports in order to have a piece of code working. If you maintain > projects in a team, you will likely have to handle patches that you > wrote along with patches that your co-workers have created. > > While this situation is not hard to handle while creating the port, it > is slightly more complex when you want to update the port in question. > You have to deal with each patch and see if it is still relevant, and > since you don't have many info about it, you first have to figure out > what it is supposed to fix. Generally, you try with / without the patch > and see if you keep it, but don't go any further (search is the bug has > been reported upstream, if solutions have been provided upstream, etc.). > > > If I consider for example the port of Mono: > http://code.google.com/p/bsd-sharp/source/browse/trunk/lang/mono/files > > We have 13 patches I want to review in order to cleanup the port. > > I would like to ask random questions like: > - who made this patch? [*] > - what is-it supposed to do? [*] > - has it been reported upstream? where? > - is it fixed in projects trunk upstream? > - will it expire at some point (e.g. trunk has been fixed after > foo-1.0.1 was tagged so the patch will be useless as soon as foo is > at version>1.0.1) > > Questions marked with a * can be answered directly using some version > control system (even if in my case it will not help much since most > patches come from revision 3: =ABInitial import: copy of the cvs repo.=BB= ). > > > I am so wondering if anyone has ever setup some tools to ease > collaborative ports maintenance? > > > Thanks! > Romain No, but setting up svk is the best way to maintain local patches against a repository. I have yet to set it up though because I haven't taken the time to do so yet. -Garrett