Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Feb 2004 10:50:35 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        "Vladimir B. Grebenschikov" <vova@express.ru>
Cc:        "current@freebsd.org" <current@freebsd.org>
Subject:   Re: HEADS UP: MAJOR changes to the ports system
Message-ID:  <20040204185035.GB26210@xor.obsecurity.org>
In-Reply-To: <1075893137.779.43.camel@localhost>
References:  <Pine.BSF.4.21.0402040021500.71519-100000@InterJet.elischer.org> <1075883492.76993.65.camel@shumai.marcuscom.com> <1075893137.779.43.camel@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help

--3uo+9/B/ebqu+fSQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 04, 2004 at 02:12:29PM +0300, Vladimir B. Grebenschikov wrote:
> ? ??, 04.02.2004, ? 11:31, Joe Marcus Clarke ?????:
> > 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 u=
sers
> > > > hear this.  Two _MAJOR_ changes just went in to the ports tree that=
 are
> > > > 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 abo=
ut
> > > 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.
>=20
> 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.

Not any more...you're out of date :-)

Kris

--3uo+9/B/ebqu+fSQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAIT76Wry0BWjoQKURAlzSAJoCI/r1Cnu7xr+HSnF7cJ4elKp0tQCgxWan
RE7uWbdX4NV+cRj6gaC6b5o=
=bIk+
-----END PGP SIGNATURE-----

--3uo+9/B/ebqu+fSQ--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040204185035.GB26210>