Re: pkg/36437 (planner build fails)

[Ondřej Tůma <pkgsrc%blackmouse.biz@localhost>]

The following reply was made to PR pkg/36437; it has been noted by GNATS.

From: =?ISO-8859-2?Q?Ond=F8ej_T=F9ma?= <pkgsrc%blackmouse.biz@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/36437 (planner build fails)
Date: Mon, 04 Jun 2007 21:48:07 +0200

 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
 --------------enig7BFACF49F4E83F4191A7B016
 Content-Type: text/plain; charset=ISO-8859-2
 Content-Transfer-Encoding: quoted-printable
 
 
 Julio M. Merino Vidal napsal(a):
 >  so if you can disabled python, you must tell it to configure :(
 > =20
 >  I know.  I am asking what the python support brings us and if that is
 >  really useful.  If not it is easier to simply disable it.
 
 In fact, i never use it, but the bindigs look well, and there is area
 for new functions (better integration with dia, cvs or svn, some editors
 which have python bindigs and so on), so ...
 
 >  > In my
 >  >  opinion, there could be good idea, to build python support at =3D20=
 
 >  > least via
 >  >  PKG_OPTION.
 > =20
 >  No, sorry, no options here.  This python support is something that =3D=
 20
 >  can be built and installed by a separate package so using options is =3D=
 20
 >  wrong.
 
 if could be build separetly, i have no objections.
 
 
 --------------enig7BFACF49F4E83F4191A7B016
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.7 (GNU/Linux)
 
 iD8DBQFGZGx7BmNIPxOnb/IRAudWAKCtWXh4xwX4/WVJzwzHqJ1iy2O6EQCgptdS
 gbGj1g1zlQhCSPYZBDPliJw=
 =5SPA
 -----END PGP SIGNATURE-----
 
 --------------enig7BFACF49F4E83F4191A7B016--