Re: installation error on SuSE 10.1

["David Van Ginneken" <..hidden..>]

On 9/22/06, Alejandro Imass <..hidden..> wrote:
> Don't use that script IMHO.
>
> Here is a recipe I use:
>
> 1) Make sure you have the plpgsql lang installed in your template1 db
> (man createlang)
> 2) Make sure that your pg_hba.conf will ask for a password. See
> PostgreSql doc.
> 3) create a db user with password (ledgersmb would be a nice name): as
> postgres (su - postgres) createuser ledgersmb -P . You must test that
> ledgersmb can login to template1 by doing psql -U ledgersmb -W it sould
> as for a password and let you in. If not, recheck your pg_hba.conf and
> restart postgresql for testing.
> 4) Untar the program in your web directory. Don't know where SuSe has it
> but I think it's LSB so it should be in /var/www . To make sure, look at
> your apache conf. Make sure you change the ownership of these file to
> your web daemon's name (chown -R www-data.www-data yourledgesmbdir).
> 5) Configure your httpd.conf file or site file (apache2) and make sure
> you have perl cgi handler and adequate permisions. Here is an example
> config:
>
> AddHandler cgi-script .pl
> Alias /whatever /var/www/yourledgesmbdir
> <Directory /var/www/yourledgesmbdir>
>         Options ExecCGI Includes FollowSymlinks
>         DirectoryIndex login.pl
>         Order allow,deny
>         #Allow from 172.16.2.0/255.255.255.0 ::1/128
>         Allow from all
> </Directory>
> <Directory /var/www/yourledgesmbdir/users>
>         Options None
> </Directory>
>
> You should point your browser to
>
> http://yourhost/whatever/admin.pl
>
> and be able to login to create a new database, a user and off you go.
>
>
> On Fri, 2006-09-22 at 12:58 +0200, roelof wolters wrote:
> > Hello,
> >
> > I want to install ledgerSMB on my SuSE 10.1 box.
> >
> > I have postgresl and apache running.
> >
> > When I run the setup script as root it tells me:
> >
> > Checking for latest version number .... Can't "last" outside of a loop
> > block at setup.pl line 282.
> >
> > I don not know much about Perl coding, and maybe I have overlooked
> > something fundamental but I get stuck here.
> >
> > Please,
> > anyone who can help me out?
> >
> > Any suggestion or help will be very much appreciated!
> >
> > Roelof
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys -- and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________ Ledger-smb-users mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Ledger-smb-users mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users

The new setup script also checks for required perl modules and
attempts to install them if they are missing.  As the project uses
more modules from CPAN, We're going to need to make sure that those
modules are in fact installed prior to completing the setup, else
we're going to potentially have many help requests for why there are
missing module errors.  Granted the current logic will not work for
brand new modules required with a particular build yet.  (Since the
new setup.pl with new required modules is included in the tarball, not
the one that is currently executing.)  Unless, I guess we could change
it to get a listing of "required" modules for a particular release
which would be included in the tarball after it is unzipped.  I'm sure
we could even prompt them if they want to lock down the application by
IP range during the setup and make the appropriate change.

Just some random thoughts :)