On Mon, Jan 30, 2006 at 11:57:03PM +0100, Bernd Ahlers wrote:
> Nikolay Sturm [Mon, Jan 30, 2006 at 08:03:40PM +0100] wrote:
> >* Bernd Ahlers [2006-01-30]:
> >> Comments, oks?
> >
> >Is this supposed to be this way?
> >...
> >checking for a Python interpreter with version >= 2.0... none
> >configure: WARNING: Disabling fetchmailconf: python 2.0 or greater not found
> >...
> >
> Our ${LOCALBASE}/bin/fetchmailconf is a wrapper script for the real
> fetchmailconf binary. It spits out an advice to install python if you
> want to run this utility. We install the fetchmailconf regardless of
> python is installed during build time or not.
>
> This script exists for a long time and I like it. Because I don't have
> to install python to install/build fetchmail.
>
> But that's just me. Other opinions or good reasons against it?
I don't care for fetchmailconf, but would really dislike having to get
all of python everytime I install fetchmail. Since what the port does
now makes this possible, I'd not bother changing stuff (like adding a
flavour).
Joachim
