cvs commit: ports/converters/p5-Text-Bidi pkg-descr
pkg-descr ports/deskutils/p5-ZConf-BGSet pkg-descr
ports/devel/p5-App-SVN-Bisect pkg-descr ports
az at freebsd.org
Sun Feb 13 16:37:01 UTC 2011
Jesus Christ! it changes everything. Thanks for pointing and explaining. I
was almost already do touch 226 ports.
Since guidelines is outdated maybe put your explanation somewhere on WIKI
under portmrg@ section?
On Sun, Feb 13, 2011 at 7:07 PM, Erwin Lansing <erwin at freebsd.org> wrote:
> On Sun, Feb 13, 2011 at 05:29:32PM +0300, Andrej Zverev wrote:
> > Pardon me but I thought what sweeping commit = affect huge number of
> > which cluster required to rebuild.
> > Since my commit don't touch PORTVERSION or PORTREVISION(PORTEPOCH). I
> > thought it's okay.
> > So, what actually sweeping commit? Don't touch more then 10,20 ports per
> > commit?
> > How my changes affect on package building? If I broke something I'm ready
> > fix.
> I guess we'll need to update the guidelines to be more specific,
> especially after the change towards the soft-freeze we have used the
> last few releases. During the soft-freeze, it has everything to do with
> package building, so here we are most careful about functional changes
> that may break functionality requiring either large rebuilds or other
> time consuming fixes that may delay the release. During the slush, as
> we have now, it's all about potential rebuilds and retagging. As the
> tree has been tagged, commits will no longer affect what goes into the
> release, but if a security vulnerability turns up requiring a refresh of
> a given package, if that ports has changed all those changes, including
> things like shared library bumps etc, will have to be brought in as well
> as we can only move the tag forwards. It's a tag, not a branch.
> I hope that explains it a bit more in detail, but you're right that the
> current guidelines are outdated and should be clarified.
More information about the cvs-ports