Subject: Re: pkg/36437 (planner build fails)
To: None <,,,>
From: Julio M. Merino Vidal <>
List: pkgsrc-bugs
Date: 06/04/2007 17:40:05
The following reply was made to PR pkg/36437; it has been noted by GNATS.

From: "Julio M. Merino Vidal" <>
Cc: Ondrej Tuma <>
Subject: Re: pkg/36437 (planner build fails)
Date: Mon, 4 Jun 2007 19:37:01 +0200

 On 04/06/2007, at 19:25, Ond=C5=99ejT=C5=AFma wrote:
 >  Hi,
 >  Here is full log:
 > 20070603.2003=3D
 >  /time/planner/.broken.html
 >  so if you can disabled python, you must tell it to configure :(
 I know.  I am asking what the python support brings us and if that is =20=
 really useful.  If not it is easier to simply disable it.
 > In my
 >  opinion, there could be good idea, to build python support at =20
 > least via
 No, sorry, no options here.  This python support is something that =20
 can be built and installed by a separate package so using options is =20
 >  In other thing, there isn't this line in Makefile like in wip/planner
 >  which is good idea,
 Yep, didn't remember about that.
 >  p5-XML-Parser>=3D3D2.31nb1 is not need for build now ?
 It is generally never needed because it is an intltool requirement, =20
 not one that comes from the real program.
 >  And why isn't this line in new packages in pkgsrc ?:
 >  USE_LANGUAGES=3D3D=3D09=3D09c c++
 >  I know, it's only warning, but that's not means it's ok !!
 Didn't notice it.
 >  at the end, what i know, wip/planner is tested on a few platforms, =20=
 > so it
 >  is good idea to get packages from wip if exists and if they are =20
 > actual.
 Generally yes.  Except that I did not see your package in the first =20
 Julio M. Merino Vidal <>