cvs commit: ports/x11/libX11 Makefile distinfo manpages
pkg-plist ports/x11/libX11/files patch-src_ImUtil.c
eric at anholt.net
Wed Jun 6 23:51:54 UTC 2007
On Wed, 2007-06-06 at 17:41 -0400, Kris Kennaway wrote:
> On Wed, Jun 06, 2007 at 11:24:44PM +0200, Pav Lucistnik wrote:
> > Kris Kennaway p??e v st 06. 06. 2007 v 16:04 -0400:
> > > On Wed, Jun 06, 2007 at 04:25:03PM +0000, Pav Lucistnik wrote:
> > > > pav 2007-06-06 16:25:03 UTC
> > > >
> > > > FreeBSD ports repository
> > > >
> > > > Modified files:
> > > > x11/libX11 Makefile distinfo manpages pkg-plist
> > > > Removed files:
> > > > x11/libX11/files patch-src_ImUtil.c
> > > > Log:
> > > > - Update to 1.1.2
> > > > - Don't remove lib/X11, it's in mtree
> > >
> > > BTW, we had decided not to do minor updates to the X.org ports without
> > > a good reason. The disruption caused by frequent tiny updates is
> > > tremendous.
> > Why not? There are no consequences in updating to dot-dot releases here.
> > I was told by flz and anholt that I'm free to help out keeping X ports
> > up to date.
> The main consequences are:
> * Forcing the package clusters to frequently rebuild all of X, slowing
> down all package builds and the rate at which we can do other testing
> on pointyhat.
> * The inevitable problems with commits to "deep" ports like this one
> which will take out most of the ports tree when they fail to build,
> leading to yet more delays in publication of usable package sets.
> What was decided was to only update in batches when x.org makes a new
> "kamikaze" release (or whatever they are calling it ;), unless there
> is a really good reason to update a port otherwise.
That's an unfortunate policy, given that generally X developers can only
be bothered to make releases when there's an important fix to push
out(*). In this libX11 case, this point release included stability and
security fixes. I suggested to Pav that libs updates were a good thing
to do, since they're generally bugfixing and such, unlike drivers and
the server (and the protos they depend on) where more context is
* The exception to this in the past has been at katamari time, when we
were rolling up any modules with trivial changes that developers hadn't
been bothered to release already. I think I've successfully killed that
part of the katamari process.
Eric Anholt anholt at FreeBSD.org
eric at anholt.net eric.anholt at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20070606/14394c67/attachment.pgp
More information about the cvs-all