Date: Wed, 25 Mar 2009 18:18:49 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: obrien@freebsd.org, Wesley Shields <wxs@freebsd.org> Cc: cvs-ports@freebsd.org, Pav Lucistnik <pav@freebsd.org>, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/shells/bash Makefile pkg-plist Message-ID: <p06240800c5f05d3db740@[128.113.24.47]> In-Reply-To: <20090324043028.GA34952@dragon.NUXI.org> References: <200903120954.n2C9s2ev063133@repoman.freebsd.org> <20090313023956.GA49511@dragon.NUXI.org> <49BA52D2.8090209@FreeBSD.org> <20090323231412.GA94221@hub.freebsd.org> <20090324012325.GB1292@atarininja.org> <20090324043028.GA34952@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 9:30 PM -0700 3/23/09, David O'Brien wrote: >On Mon, Mar 23, 2009 at 09:23:25PM -0400, Wesley Shields wrote: >> On Mon, Mar 23, 2009 at 11:14:13PM +0000, David O'Brien wrote: >> > On Fri, Mar 13, 2009 at 01:34:26PM +0100, Pav Lucistnik wrote: >> > > David O'Brien wrote: >> > > >There is zero reason to force a reinstall for a PLIST change. >> > > >Either the port is already installed (and the user can wait for >> > > >some other reason to update), or the port isn't installed and >> > > >bumping PORTREVISION does nothing. >> > > > > > > It's needed for package cluster, otherwise it does not know to > > > > rebuild and will serve incomplete package forever. > > > >> > Is there ever a change then that doesn't require a bump in either >> > PORTREVISION or PORTVERSION? >.. >> Just changing the maintainer should not require the user to do anything. > >That is the only case I can think of. Even changing the comment or >pkg-descr should have its PORTREVISION bumped in order to get a new >package built so users have the fresh description. Ew, I don't like that at all. Why should I rebuild (say) bash just because someone fixes a typo in the description? The port is already installed, and I have no intention of reading the description until *maybe* the next time the package really does change. It's probably not that big a deal for bash, which is fairly easy to build and well-behaved. Now let's change the pkg-descr for some key component of Gnome, and have people spend a day to rebuild it and everything that depends on it, just because a description changed? In a file that no one is reading given that the port is already installed? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06240800c5f05d3db740>