Chris Travers wrote:
Thanks for the reply, but that concerns me somewhat. I was quite glad that I got something that appears to be running by just installing it from RPM's on my target machine and not needing any development tools or libraries to be installed. I am wary of having that sort of tools (incl. GCC) laying around on a production machine.Your DBD::Pg is out of date. Update it through whatever method you used the first time around. If updates are not available, please use CPAN (you will need the postgresql header files for this). Since I started with LedgerSMB about a year ago, I got it running fairly easily and sort of out of the box on my production machine and have kept track of updates up to approx. 1.12 and this is what I currently run my live accounting on. I spend significant time getting it 'nice' with all the templates and such and fixed a very minor thing or two to make sure that every Latex template could use the same document header and have all the variables expanded properly. I 'hit' a few problems that I now simply avoid. However, since then I have tried several times to get a more recent version up and running but so far without luck. I am quite reasonable around Linux and scripts and can find my way around perl a bit but I an definitively not a perl programmer. As such, I found the requirement to use CPAN for updates to get the later versions LedgerSMB running pushing me way beyond my comfort zone as it seems to be updating and installing way more than I comfortable with. In some attempts to get it the later versions running, tried several times over the past 6 to 8 months to ledgerSMB 1.2x installed and running and did use CPAN. But every time, I tried, I ended up in a situation where CPAN failed to update something properly or asked me for questions that I could not answer (e.g. provide the path to a particular file for which I had no idea where that file had to come from or what else I needed to install to get that file). So I gave up and wasn't feeling really good as to were LedgerSMB was heading. It seemed to be requiring more and more obscure libraries that made it almost impossible to install on the generic machine that I was using (SME Server based on CentOS/RHEL 4). I actively looked at other open source accounting facilities for an alternative. Then last week, I gave it another go with LedgerSMB on a completely new and bare installed of a new test machine (in VMware). I went through all the steps of installing postgres from rpms. I also was able to install a few perl rpms and installed 1.2.9 of LedgerSMB from the tar file. At that stage the LedgerSMB perl ./Build.PL was reporting no errors or missing packages and I was getting exited again when I got to a login screen and could create and create a new database and user and login on the LedgerSMB login screen. Then I tried to create a new customer and hit the described error :-( and you tell me I have to use CPAN to update again. On my SME Server/CentOS4 system, 'rpm -q perl-DBD-Pg' is 'perl-DBD-Pg-1.32-1.el4.rf', was last updated 11 October 2007 and as far as I can tell, this is the latest version available for el4. So I am not sure where that leaves me. My production system is up-to-date with the latest updates from the 'SME Server', but the transition to SME Server 8.0 / CentOS5 is still a little while away and that means I am stuck and can't update to the latest LedgerSMB. I find it a worry if applications impose requirements for the 'latest & greatest' and leave slightly older systems out in the cold. I am sorry that this turned a bit into a rant, but I just had to get some 8 months of frustration of not being able to get LedgerSMB 1.2.x running of my chest and I hope that some consideration can be given to sticking to older libraries so that LedgerSMB can be installed easily on a broader range of systems or that these libraries can be integrated transparently into the LedgerSMB tree so that it the ledgerSMB tree can be dropped in place and requires minimum external libraries from the system on which it is installed. Best regards, Marco --
Marco Hess
This message is for the addressee only and may contain confidential information. You must delete and not use it if you are not the intended recipient. Any views expressed in this message are those of the individual sender. This message is for information purposes only. All liability of Through IP Pty. Ltd. and its entities for any damages resulting from e-mail use is excluded. Through IP Pty. Ltd. and its entities do not guarantee and takes no liability for the integrity, confidentiality or timeliness of messages exchanged over the Internet or for any damages resulting from e-mail use. By corresponding with Through IP Pty. Ltd. and its entities through the Internet you acknowledge and accept those risks. |