Re: [Ledger-smb-devel] LedgerSMB 1.4-M1_4635 is out

2012-03-31 Thread Philip Rhoades
Chris, On 2012-03-31 00:48, Chris Travers wrote: > On Fri, Mar 30, 2012 at 7:13 AM, Philip Rhoades > wrote: >> Chris, >> >> Error logs look the same as before - did you get my previous post >> with >> the other ones I sent?  Because of the size, I got a message that >> the >> post would need

Re: [Ledger-smb-devel] Is the requirement list up-to-date?

2012-03-31 Thread Robert James Clay
On Sat, 2012-03-31 at 19:56 -0400, Mikkel Høgh wrote: > I have been struggling to create a FreeBSD port for LedgerSMB 1.3 > I figured that it would be relatively straight forward to upgrade the 1.2 > makefile, > but reading the INSTALL file in 1.3, LSMB has a lot of new dependencies. > > Mo

[Ledger-smb-devel] Is the requirement list up-to-date?

2012-03-31 Thread Mikkel Høgh
Hi, I have been struggling to create a FreeBSD port for LedgerSMB 1.3 (there are ports for 1.0, 1.1 and 1.2 already). I figured that it would be relatively straight forward to upgrade the 1.2 makefile, but reading the INSTALL file in 1.3, LSMB has a lot of new dependencies. Most of these I wa

Re: [Ledger-smb-devel] LedgerSMB addons from "baby" to "teenager".

2012-03-31 Thread Chris Bennett
On Sat, Mar 31, 2012 at 07:13:36PM +0200, H?vard S?rli wrote: > > - some way to keep track of witch addons is installed >name and version > - witch file(s) each plug in brings. > I think this is going to require something natively in LedgerSMB just for the purpose of control and information

Re: [Ledger-smb-devel] Start of perl setup and drop db scripts

2012-03-31 Thread Chris Bennett
I have finished preliminary versions of these two scripts with an interactive option. These need to be cleaned up and have a few more comments added. They now offer to show possible COAs, GIFIs and country codes. I did not have putting the ledgersmb-httpd.conf in the right place up till now. Also

[Ledger-smb-devel] LedgerSMB addons from "baby" to "teenager".

2012-03-31 Thread Håvard Sørli
Continue irc discussion: " basically our plug-in infrastructure is still in its baby ages" Can we grow up? Can we do better ? Yes we can... Can we make some "best practises" for a addon ? - some way to keep track of witch addons is installed name and version - witch file(s) each plug in b