cvs commit: ports/shells/bash Makefile pkg-plist

[Gerald Pfeifer]

On Mon, 23 Mar 2009, David O'Brien wrote:
>>> 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.

Setting FORCE_MAKE_JOBS would be another example which should not 
trigger a rebuild for the user.

Or something like the following, which I had embedded in some other
lang/gcc42 changes, but would have committed by itself otherwise:
"Remove gcc-testsuite from DISTFILES, along with the post-build and
check targets.  This reduces disk and bandwidth consumptions for a
feature (apparently) never used."

Gerald