From owner-freebsd-current@FreeBSD.ORG Wed Feb 4 02:56:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF00916A4CE; Wed, 4 Feb 2004 02:56:20 -0800 (PST) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3489143D55; Wed, 4 Feb 2004 02:56:18 -0800 (PST) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.30; FreeBSD) id 1AoKj5-0000Oz-W8; Wed, 04 Feb 2004 13:57:47 +0300 From: "Vladimir B. Grebenschikov" To: Joe Marcus Clarke In-Reply-To: <1075883492.76993.65.camel@shumai.marcuscom.com> References: <1075883492.76993.65.camel@shumai.marcuscom.com> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Inc. Message-Id: <1075892266.779.33.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 04 Feb 2004 13:57:47 +0300 Sender: Vladimir Grebenschikov X-Mailman-Approved-At: Wed, 04 Feb 2004 05:09:46 -0800 cc: "current@freebsd.org" Subject: Re: HEADS UP: MAJOR changes to the ports system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 10:56:20 -0000 =F7 =D3=D2, 04.02.2004, =D7 11:31, Joe Marcus Clarke =D0=C9=DB=C5=D4: > On Wed, 2004-02-04 at 03:22, Julian Elischer wrote: > > On Wed, 4 Feb 2004, Joe Marcus Clarke wrote: > >=20 > > > Sorry for the wide distribution, but it is critical that -CURRENT use= rs > > > hear this. Two _MAJOR_ changes just went in to the ports tree that a= re > > > bound to cause some pain to -CURRENT users. =20 > > >=20 > >=20 > > I'm glad to hear about this and I wouldn't mind hearing regularly about > > major events over in the ports tree. >=20 > I've started doing this. The full summary was sent to ports@ and > ports-developers@, plus I added a copy to /usr/ports/CHANGES. This is > now the second major ports update I've summarized. Once the archives > get back up to speed, you should be able to see my previous summary. How about gettext -> gettext-old transition ? A lot of ports still=20 depends on gettext-old while others on gettext, gettext conflicts with=20 gettext-old, and, as result, portupgrade -af constatntly tries to install gettext-old as dependancy and fails. > Joe --=20 Vladimir B. Grebenschikov SWsoft Inc.