Re: Installation process (Was: [siesta-dev] [PATCH] Fix broken POD in Siesta.pm)

[prev] [thread] [next] [lurker] [Date index for 2003/10/17]

From: Richard Clamp
Subject: Re: Installation process (Was: [siesta-dev] [PATCH] Fix broken POD in Siesta.pm)
Date: 12:21 on 17 Oct 2003
On Fri, Oct 17, 2003 at 11:29:41AM +0100, Simon Wistow wrote:
> On Fri, Oct 17, 2003 at 02:03:10PM +0400, Ilya Martynov said:
> > Is it supposed that siesta.conf is being created during installation?
> > If yes, then there is a problem - I cannot find it. Neither in
> > ~/siesta where I told installer to install things, nor in Perl lib
> > tree where it installed libs.
> 
> It should be in ~/siesta

If you have one, that's where it should live, yes.

I'm not mad keen on the auto-creating idea, just because then we have
to dick about more during upgrades to be careful to not overwrite
someones hand-tweaked siesta.conf with our new one.

> > Now after reading INSTALL I tried to setup database:
> > 
> > [snip]
> >
> > Could it be a problem that I run blead Perl(#20173) ?

Nope.

> No, that's characteristic of there not being siesta.conf I think. 

Nope.

> Basically Class::DBI doesn't know what type of database to connect to.

It should, because the default for
$Siesta::Config::config->storage_dsn is
'dbi:SQLite:@@ROOT@@:/database' (see Config.pm.in)

If something is causing that default to be undef instead then that's a
different problem to be looked at, but I can't reproduce it here:

% perl -MSiesta::Config -le 'print $Siesta::Config::config->storage_dsn'
dbi:SQLite:/usr/local/siesta/database


> and also check to see if it exists in Siesta::Conf

Uh?  We do already:

    __PACKAGE__->load_from( $CONFIG_FILE ) if -e $CONFIG_FILE;

-- 
Richard Clamp <richardc@xxxxxxxxx.xxx>
There's stuff above here

Generated at 13:56 on 01 Jul 2004 by mariachi 0.52