From owner-freebsd-ports@FreeBSD.ORG Fri Mar 30 19:55:30 2012 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 61FCA1065672 for ; Fri, 30 Mar 2012 19:55:30 +0000 (UTC) (envelope-from scheidell@FreeBSD.org) Received: from mx2.secnap.com.ionspam.net (mx2.secnap.com.ionspam.net [216.134.223.54]) by mx1.freebsd.org (Postfix) with ESMTP id 28FCC8FC1F for ; Fri, 30 Mar 2012 19:55:29 +0000 (UTC) Received: from mx2.secnap.com.ionspam.net (unknown [10.71.0.54]) by mx2.secnap.com.ionspam.net (Postfix) with ESMTP id 1477CD23C03 for ; Fri, 30 Mar 2012 15:55:29 -0400 (EDT) X-Virus-Scanned: SpammerTrap(r) VPS-1500 2.18 at mx2.secnap.com.ionspam.net Received: from USBCTDC001.secnap.com (unknown [10.70.1.1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx2.secnap.com.ionspam.net (Postfix) with ESMTPS id F3472D23C01 for ; Fri, 30 Mar 2012 15:55:27 -0400 (EDT) Received: from MikeBook-Air.local (10.80.0.4) by USBCTDC001.secnap.com (10.70.1.1) with Microsoft SMTP Server (TLS) id 14.0.722.0; Fri, 30 Mar 2012 15:55:27 -0400 Message-ID: <4F760FB3.6020708@FreeBSD.org> Date: Fri, 30 Mar 2012 15:55:31 -0400 From: Michael Scheidell Organization: SECNAP Network Security Corp User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12 MIME-Version: 1.0 To: References: <4F732C89.3040804@FreeBSD.org> <4F733432.4020902@FreeBSD.org> <63ca1b333a310ecc2b1d1f0e1e1542a1.squirrel@mail.experts-exchange.com> <4F7338C3.8020003@p6m7g8.com> <4F733C3A.7020004@missouri.edu> <4F734524.2000400@p6m7g8.com> <4F735340.1020103@FreeBSD.org> <4F7379FD.9040802@p6m7g8.com> <20120329200243.GA76833@server.vk2pj.dyndns.org> <20120330131625.GA30070@atarininja.org> <4F75F3ED.9000508@p6m7g8.com> <4F75FA31.2030806@p6m7g8.com> In-Reply-To: <4F75FA31.2030806@p6m7g8.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FAQ on PORTREVISION bump? 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: Fri, 30 Mar 2012 19:55:30 -0000 So, lets start: Am I the only one that finds he is too stupid to actually figure this out? I think it is still the most confusing aspect of committing/maintaining. When to bump PORTREVISION: * If you think the end user needs to rebuild the port. When not to bump PORTREVION: * If you think its a noop/waste of time/cpu for the end user to rebuild the port. Ok, flesh this out: examples When to bump PORTREVISION (when you want end user to build the port) * Mandatory: o When package changes (make package) o When dependencies change (Adding USE_PERL/BUILD_PERL/GETTEXT counts) o When pkg-plist changes (except for fixing .ifdef/NOPORT(DOCS|EXAMPLES)) o When the master port changes o When PORTVERSION CHANGES (must change back to 0, delete line) o When you want to force a relink with an updated (fixed) library o If a patch fixes something in the port o If you add new functionality o If you add/delete an OPTION o If you change the default for an OPTION * port committers have authority to bump PORTREVISION maintainer (implicit) if the master port/library port/dependency port requires any dependency to fit the list above. when NOT to * just fixing .ifdef/NOPORT(DOCS|EXAMPLES)) * if port was broken on any arch. (rebuilding on existing arch is a noop, and fixed arch didn't package anyway) * Fixing typo's in pkg-message, Comment * Updating port maintainer (new one or resetting port maintainer) * just petting portlint ( after name to ), re-order sections (notice I left out pointyhat.. if it is overworked, lets send more hardware) -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell