On, Wed May 07, 2014, Glen Barber wrote:
> On Wed, May 07, 2014 at 08:57:41AM -0400, pathiaki2 wrote:
> > On 05/07/2014 08:46, Lowell Gilbert wrote:
> > >pathiaki2 writes:
> > >
> > >>/usr/ports/databases/pgtune
> > >>
> > >>It doesn't check to see if python is installed. Python is required
On 05/07/2014 09:23, Glen Barber wrote:
On Wed, May 07, 2014 at 08:57:41AM -0400, pathiaki2 wrote:
On 05/07/2014 08:46, Lowell Gilbert wrote:
pathiaki2 writes:
/usr/ports/databases/pgtune
It doesn't check to see if python is installed. Python is required to
run this.
That's strange. p
On Wed, May 07, 2014 at 08:57:41AM -0400, pathiaki2 wrote:
> On 05/07/2014 08:46, Lowell Gilbert wrote:
> >pathiaki2 writes:
> >
> >>/usr/ports/databases/pgtune
> >>
> >>It doesn't check to see if python is installed. Python is required to
> >>run this.
> >That's strange. pgtune defines USE_P
On 05/07/2014 08:46, Lowell Gilbert wrote:
pathiaki2 writes:
/usr/ports/databases/pgtune
It doesn't check to see if python is installed. Python is required to
run this.
That's strange. pgtune defines USE_PYTHON, which adds python to both the
build and run dependencies. It *should* work
pathiaki2 writes:
> /usr/ports/databases/pgtune
>
> It doesn't check to see if python is installed. Python is required to
> run this.
That's strange. pgtune defines USE_PYTHON, which adds python to both the
build and run dependencies. It *should* work correctly...
__