cvs commit: ports/x11-toolkits/py-wxPython24 Makefile
kris at obsecurity.org
Thu May 12 19:48:36 PDT 2005
On Thu, May 12, 2005 at 10:39:10PM -0400, Adam Weinberger wrote:
> Kirill Ponomarew wrote:
> >On Thu, May 12, 2005 at 06:17:19PM -0400, Adam Weinberger wrote:
> >>Kirill Ponomarew wrote:
> >>>krion 2005-05-12 20:59:16 UTC
> >>>FreeBSD ports repository
> >>>Modified files:
> >>> x11-toolkits/py-wxPython24 Makefile
> >>>Fix INDEX build.
> >>>Revision Changes Path
> >>>1.48 +1 -1 ports/x11-toolkits/py-wxPython24/Makefile
> >>This wxGTK stuff has been a pretty big change. Can the ports tree be
> >>completely thawed now? There have been a ton of changes, and I don't
> >>exactly see the point of us still being in a partial ports freeze. The
> >>FreeBSD GNOME team has been holding off on some updates (e.x. gettext)
> >>for the thaw.
> >Slush is over when RELEASE is announced, it's described on:
> If that's the answer I was looking for, I could have read it off the
> page myself.
> Perhaps I need to rephrase: why do we have a ports slush if we don't
> adhere to its terms? Please don't say "because it's the third item on
> the page."
This commit occurred after the release of 5.4-RELEASE. The 'freeze
status' was updated on the website already (by someone else, after
confirming with portmgr), although I don't think an accompanying email
notification was sent by portmgr.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20050512/6b61df64/attachment.bin
More information about the cvs-all