From owner-freebsd-doc@FreeBSD.ORG Mon Nov 13 23:00:58 2006 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9301016A4EA for ; Mon, 13 Nov 2006 23:00:58 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 984D643D90 for ; Mon, 13 Nov 2006 23:00:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kADN0Cxs061118 for ; Mon, 13 Nov 2006 23:00:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kADN0CH6061117; Mon, 13 Nov 2006 23:00:12 GMT (envelope-from gnats) Date: Mon, 13 Nov 2006 23:00:12 GMT Message-Id: <200611132300.kADN0CH6061117@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Pav Lucistnik Cc: Subject: Re: docs/105494: [PATCH] PH: rewrite WxWidgets entry X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pav Lucistnik List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 23:00:58 -0000 The following reply was made to PR docs/105494; it has been noted by GNATS. From: Pav Lucistnik To: Alejandro Pulver Cc: FreeBSD gnats submit Subject: Re: docs/105494: [PATCH] PH: rewrite WxWidgets entry Date: Mon, 13 Nov 2006 23:52:28 +0100 > >Number: 105494 > >Synopsis: [PATCH] PH: rewrite WxWidgets entry Some comments on your patch: - please keep using wxWidgets, with small first w. That's how the project is called, check http://www.wxwidgets.org/ for proof - please be consistent with double space after full stop - > + be modified to found the expected version. Fortunately most of the - to find the expected version > + applications call the wx-config script to > + determine the necessary compiler and linker flags, which is named > + differently for all the available versions, and the majority of them > + also have a variable or accept a parameter to allow modifying > + it. Otherwise the applications could be modified to use one of - this overly long sentence is confusing! It could use a split into four standalone, clear ones. What about Fortunately, most of the applications call the wx-config script to determine the necessary compiler and linker flags. The script is named differently for every available version. Majority of applications respect an environment variable, or accept a configure argument, to specify which wx-config script to call. Otherwise they have to patched. > + The following is a list of available > + WxWidgets versions and the corresponding > + port in the tree: - corresponding ports > + The 2.6 version also comes in Unicode and - also comes in Unicode - version? variant? modification? > + WxPython - wxPython > + WxMozilla - wxMozilla > + WxSVG - wxSVG > + The dependency type added when you select each component can be > + manually specified by adding a suffix separated by a > + :, or a default value will be used. The available - this is confusing, please rephrase. The dependency type can be selected for each component by adding a suffix separated by a semicolon. > + The following variables are defined after defining one of the > + variables from . - overuse of defined. What about The following variables are available in the port: > + wxrc program (with differen name) - with different name > + you modify the Lua port variables - should this really read Lua? > + Lua interpreter to obtain the full - again, should this read Lua? Awaiting corrected patch. -- Pav Lucistnik Some programmers are able to write FORTRAN in any language.