cvs commit: ports/Mk bsd.wx.mk
pav at FreeBSD.org
Sun Dec 31 09:05:49 PST 2006
Sergey Matveychuk píše v ne 31. 12. 2006 v 18:40 +0300:
> Pav Lucistnik wrote:
> > Sergey Matveychuk píše v ne 31. 12. 2006 v 16:10 +0300:
> >> Erwin Lansing wrote:
> >>> This broke INDEX as there is no x11-toolkits/py-wxPython28 port and this
> >>> is now detected.
> >> As I investigated it affects only on audio/py-karaoke port. So I'll
> >> commit a fix for this port that looks quite correct anyway:
> >> -USE_WX= 2.4+
> >> +USE_WX= 2.4-2.6
> > So once 2.8 comes out, you promise to revisit this port?
> The port should be checked with 2.8. I'm not sure it'll work with 2.8.
The original author felt confident that the port will work with a future
releases of wxPython, thus he put 2.4+ in the port.
If he would not be sure, he would put 2.4-2.6 in there straight away.
When we add a new gcc version, we don't check all ports if they work.
We assume everything will work, and fix or mark the cases where there's
a problem. Why we should treat wxPython any different?
Pav Lucistnik <pav at oook.cz>
<pav at FreeBSD.org>
Sun couldn't care less about Linux other than it now being necessary
in order to be buzzword compliant.
-- Al Dente
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?=
Url : http://lists.freebsd.org/pipermail/cvs-ports/attachments/20061231/d6980369/attachment.pgp
More information about the cvs-ports