From owner-freebsd-x11@FreeBSD.ORG Fri Jun 8 01:21:34 2007 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E21C516A580; Fri, 8 Jun 2007 01:21:33 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id CAFE113C483; Fri, 8 Jun 2007 01:21:33 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E4F201A4D95; Thu, 7 Jun 2007 18:21:33 -0700 (PDT) Received: from rot13.obsecurity.org (rot13.obsecurity.org [192.168.1.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 20B32512AB; Thu, 7 Jun 2007 21:21:33 -0400 (EDT) Received: by rot13.obsecurity.org (Postfix, from userid 1001) id 0B043C217; Thu, 7 Jun 2007 21:21:33 -0400 (EDT) Date: Thu, 7 Jun 2007 21:21:33 -0400 From: Kris Kennaway To: Dejan Lesjak Message-ID: <20070608012133.GA32989@rot13.obsecurity.org> References: <200706061625.l56GP3lo043614@repoman.freebsd.org> <20070607102229.98t8ak5kmoo8woco@webmail.leidinger.net> <20070607091605.GB22049@rot13.obsecurity.org> <200706080308.31808.dejan.lesjak@ijs.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706080308.31808.dejan.lesjak@ijs.si> User-Agent: Mutt/1.4.2.2i Cc: freebsd-x11@freebsd.org, Florent Thoumie , Kris Kennaway , Eric Anholt , Pav Lucistnik , Mark Linimon , Alexander Leidinger Subject: Re: cvs commit: ports/x11/libX11 Makefile distinfo manpages pkg-plist ports/x11/libX11/files patch-src_ImUtil.c X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2007 01:21:34 -0000 On Fri, Jun 08, 2007 at 03:08:30AM +0200, Dejan Lesjak wrote: > [moving to freebsd-x11@] > > On Thursday 07 June 2007 11:16:05 Kris Kennaway wrote: > > On Thu, Jun 07, 2007 at 10:22:29AM +0200, Alexander Leidinger wrote: > > > Quoting Mark Linimon (from Wed, 6 Jun 2007 > > > > > > 20:55:38 -0500): > > > >On Wed, Jun 06, 2007 at 09:44:50PM -0400, Kris Kennaway wrote: > > > >>The FreeBSD project does not have the resources (or desire) to > > > >> effectively do full-time incremental X.org release engineering because > > > >> of X.org changes being continuously pushed into ports. > > > > > > Who decides what is going in and what not? What changes are allowed to > > > go in and which aren't (read: what's the definition of "important" > > > here)? > > > > "Fixes an application crash" or "Fixes a security vulnerability" would > > be good reasons. "Fixes some manpage typos" or "Adds a new cursor > > theme" or "Adds some linux-specific cruft" would not be :-) I don't > > want to have to be the guardian of this myself so I hope the x11@ > > mailing list will self-regulate with a bit of guidance. > > > > Basically everyone needs to be aware that commits to x.org core ports > > (those in the dependency path of xorg-libraries, basically) need to > > come with a clear justification of why the update is required, so if > > you are prepared to defend yourself with solid arguments on that point > > then you probably have a reason to proceed. > > Picking more or less random message... > I don't think this is such a big deal actually. This is mostly about > xorg-libraries dependencies (the core x.org ports) and they will probably not > get new versions released that often (eg. last libX11 release was 30 Nov > 2006) by X.org themselves. And then there are releases that might as well be > skipped alltogether (libXcomposite 0.3.2 comes to mind); we already have > http://wiki.freebsd.org/PortsNotUpgraded to annotate those. > There will probably be more frequent updates of ports right now, though, as we > find some regressions and other stuff missed in testing as more people with > various environments get to install the thing. > As for this specific upgrade, it was indeed of the "Fixes an application > crash" and "Fixes a security vulnerability" type and as said happened a bit > more than 6 months after last release. That's fine, Pav just didn't make that clear (and was in fact unaware of the policy we'd decided). We are on a learning curve so will have to see how things go in practise. Kris