[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: gem'izing ruby-gnome2-*?
> On Sat, Jan 23, 2016 at 10:51:49AM +0900, Izumi Tsutsui wrote:
> > I've put updated shar, which is tested on NetBSD/amd64 7.0 and
> > pkgsrc HEAD (around 20160120) with "RUBY_VERSION_DEFAULT=22":
> > https://gist.github.com/tsutsui/caa5ebc96b4ececa909c
> > Note PKGNAMEs and PKGREVISIONs are not changed/bumped.
> These package fine for me.
> Please commit this.
According to pkgsrc guide, it looks we should also bump PKGREVISIONs
because at least PLISTs and (some) dependencies are updated:
>> PKGREVISION should be incremented for any non-trivial change
>> in the resulting binary package.
>> Examples of changes that do not merit increasing PKGREVISION are:
>> - Changing HOMEPAGE, MAINTAINER, OWNER, or comments in Makefile.
>> - Changing build variables if the resulting binary package is the same.
>> - Changing DESCR.
>> - Adding PKG_OPTIONS if the default options don't change.
>> Examples of changes that do merit an increase to PKGREVISION include:
>> - Security fixes
>> - Changes or additions to a patch file
>> - Changes to the PLIST
>> - A dependency is changed or renamed.
How should we handle the "merit" in this case?
Main Index |
Thread Index |