Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Feb 2007 22:34:27 -0600
From:      "Jeremy Messenger" <mezz7@cox.net>
To:        "Ade Lovett" <ade@freebsd.org>
Cc:        Peter Johnson <johnson.peter@gmail.com>, freebsd-ports@freebsd.org
Subject:   Re: Impending update to devel/gettext
Message-ID:  <op.tntqzpt69aq2h7@mezz.mezzweb.com>
In-Reply-To: <813FE72F-0F37-4321-8B28-AA67CB352FC7@freebsd.org>
References:  <45D17582.2010908@gmail.com> <813FE72F-0F37-4321-8B28-AA67CB352FC7@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 15 Feb 2007 22:01:03 -0600, Ade Lovett <ade@freebsd.org> wrote:

>
> On Feb 13, 2007, at 00:23 , Peter Johnson wrote:
>> The correct fix is probably a patch to the gettext configure script t=
o  =

>> disable the check for gmkdir.
>
> Hi Peter,
>
> Please see http://www.lovett.com/ade/freebsd/gettext-4.diff
>
> MD5 (gettext-4.diff) =3D 792085ea01e8242e7e0260bad3336efd
>
> This should address your issues with sysutils/coreutils being around, =
 =

> and gettext picking up on gmkdir.

I have updated it in MC without bump it, but I always can bump it for  =

gmkdir issue if one of my team request. Is it rare? If it is, then I thi=
nk  =

anyone can always reinstall it. :-)

> Everyone,
>
> In addition, as part of the ongoing cleanup of the tree as a result of=
  =

> the deprecation of 4.x for the ports world, devel/gettext will now FAI=
L  =

> (strangely) on 4.x.  This is on purpose, and I have no plans to change=
  =

> things back.  I'm not even going to put in a "BROKEN on 4.x" stanza,  =

> since work is underway to remove those from the tree.
>
> Naturally, with the number of ports depending on devel/gettext, this  =

> will be a pretty good sledgehammer blow.

Sounds good, I think that Kris said that 4.x support are going to be gon=
e  =

in our tree (include bsd.*.mk) sometime soon (unsure on when, but soon).=


> Assuming no further issues, I will be committing this update on or  =

> around 1st March 2007.
>
> Thanks to everyone who has provided input on this patch to date.

There is no issue with GNOME 2.17/2.18 in MC so far.

Cheers,
Mezz

> -aDe


-- =

mezz7@cox.net  -  mezz@FreeBSD.org
FreeBSD GNOME Team  -  FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/  -  gnome@FreeBSD.org
http://wiki.freebsd.org/multimedia  -  multimedia@FreeBSD.org



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