From owner-cvs-all Tue May 22 15:45:21 2001 Delivered-To: cvs-all@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 161B037B42C; Tue, 22 May 2001 15:45:16 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA98502; Tue, 22 May 2001 15:44:44 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3B0AEBDC.A656B47F@DougBarton.net> Date: Tue, 22 May 2001 15:44:44 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Neil Blakey-Milner , Brian Somers , Ying-Chieh Liao , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/net/socks5 Makefile pkg-plist References: <200105170926.f4H9Qab60547@hak.lan.Awfulhak.org> <20010517160707.A5538@rapier.smartspace.co.za> <20010517103910.A52819@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Thu, May 17, 2001 at 04:07:08PM +0200, Neil Blakey-Milner wrote: > > On Thu 2001-05-17 (10:26), Brian Somers wrote: > > > Is a PORTREVISION bump necessary for doc/example fixes ? > > > > > > To me, a PORTVERSION change means I need to rebuild & reinstall the > > > > Strictly, it should occur whenever the generated package is different in > > any way. Theoretically we should also bump it if something like a > > static archive that it relies upon gets changed, and things like that. > > If done properly, it can help maintain as high a standard as Debian > > usually enjoys in binary package dependencies and upgrades. > > The guidelines say something like "if it's worthwhile for the user to > upgrade the package", and trivial fixes are exempted. If something > affects a dependency, it's nontrivial. Bumping it for every single change, no matter how trivial starts to create problems when users run for example pkg_version and the port revision change tells them their port is out of date. If I've got something installed and the maintainer fixes the doc installation of the port, I don't really need to recompile and reinstall. IMO we need a finer grained method of dealing with this problem. Until then I think Kris' standard here is a good one. I like the standard that says don't bump it unless the functionality of the port changes. -- I need someone really bad. Are you really bad? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message