Thus spake Alistair Crooks
> I'd prefer it if we kept it as a separate package.  That way, people
> who want it can install it.  People who don't want it don't need to
> install it.

OK.

> We just split ispell from having things dependent on switches in
> /etc/mk.conf to being a base package, with separate dictionary
> packages.  I think most of us are convinced that that is the way to
> go.  Filling up mk.conf with switches does mean that binary packages
> can be a pain.
> 
> Including it by default means that packages grow huge, and,
> presumably, that python would become a pre-requisite package for
> postgresql.  I'm not a great fan of kitchen-sink software engineering.
>  
> > How about thinkgs like Perl?  The same thing may apply.
> 
> You mean make Perl into one huge package? What would be the benefits?

I meant building the Perl interface to Python but your arguments about
the Python interface are persuasive and apply.

-- 
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.