From owner-cvs-all Wed Aug 1 5:33:57 2001 Delivered-To: cvs-all@freebsd.org Received: from mail.musha.org (daemon.musha.org [61.122.44.178]) by hub.freebsd.org (Postfix) with ESMTP id 5615F37B401; Wed, 1 Aug 2001 05:33:49 -0700 (PDT) (envelope-from knu@iDaemons.org) Received: from archon.local.idaemons.org (archon.local.idaemons.org [192.168.1.32]) by mail.musha.org (Postfix) with ESMTP id C529D4D801; Wed, 1 Aug 2001 21:33:47 +0900 (JST) Date: Wed, 01 Aug 2001 21:33:47 +0900 Message-ID: <86bsm0ufh0.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: Sheldon Hearn Cc: ozz@FreeBSD.org.ru, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/databases/p5-BerkeleyDB Makefile ports/databases/ruby-bdb Makefile ports/databases/dbtool Makefile ports/databases/py-bsddb3 Makefile ports/devel/gconf Makefile ports/editors/nvi-devel Makefile ports/mail/postfix Makefile ports/mail/postfix/scripts ... In-Reply-To: <40963.996667153@axl.seasidesoftware.co.za> References: <86elqwuhh4.wl@archon.local.idaemons.org> <40963.996667153@axl.seasidesoftware.co.za> User-Agent: Wanderlust/2.7.1 (Too Funky) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Wed, 01 Aug 2001 13:59:13 +0200, Sheldon Hearn wrote: > On Wed, 01 Aug 2001 20:50:31 +0900, "Akinori MUSHA" wrote: > > > I think I don't have no choice but to back out the db3 port update, > > since the necessary update can only be done by the vendors of those > > db3-dependant pieces of software. > > Are you sure you want to do that? > > I have a patch for openldap2. Why not test your change (or look at > bento's errorlogs) and see how many ports are actually broken. The > situation might be manageable. Because that is a wrong approach as you pointed out and I admitted. We cannot leave (possibly) broken ports unfixed any long. I updated db 3.3.11 because I believed it was upper compatible with 3.2.9, but it turned out it wasn't. So, I'd rather back out everything this time and just wait for the vendors to announce that db 3.3 is supported in their latest versions. In the meantime, what about tweaking db3 and db3-latest ports so they can co-exist and the dependent ports can gradually switch from db3.2 to db3.3? :) -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "Freeze this moment a little bit longer, make each impression a little bit stronger.. Experience slips away -- Time stand still" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message