On Wed, 09 Apr 2008, shaker yasa wrote: > I have a question. > 1- I follow your steps to send my code to test it. but 1 - when I > donwload the ledgersmb in trunck , i found ledgersmb 1.3.
Yes, svn trunk is currently the "ledgersmb-1.3 branch". When they're ready to stabilize and prepare a release, it will move to branches/1.3. I think you wanted to svn checkout branches/1.2. > 2- I follow the insturction in Install file: but I droped ledgersmb > database and recreate a new one. In the end I couldn't find the > user_conf table. I can't open the admin page. Do you think, I made > something wrong. advise me please > Shaekir trunk (also known as 1.3) is currently missing through-the-web setup automation for users (roles), permissions, etc. There are many steps you must complete to bootstrap 1.3 at this time. The developers are polishing up that part now, I think. I think you'll find it much more familiar to run branches/1.2. You only need to satisfy the dependencies, make your apache configuration, and then create a short ledgersmb.conf. $ svn co https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/branches/1.2 ledgersmb12 (that's all on one line) ledgersmb12 $ cat ledgersmb.conf [globaldb] DBname = ledgersmb DBhost = localhost DBport = 5432 DBUserName = ledgersmb DBPassword = YOURPASSWORD You can make your modifications, test, and submit patches as the result of: ledgersmb12 $ svn diff > mypatch.patch >> On Fri, 29 Feb 2008 15:29:46 -0500 >> Jeff Kowalczyk <[EMAIL PROTECTED]> wrote: >> >> shaker yasa wrote: >> > Question: what format should changes be submitted to the group in, >> > the entire file with changes commented or just the new code with >> > instructions for inserting? >> >> Without presuming to speak for the committers, the usual way a >> shared-respository project accepts changes is to: >> >> 1) svn checkout the appropriate branch (currently active are /trunk >> and /branches/1.2) >> >> 2) Make and test your changes to the local working copy. >> >> 3) svn diff and save the resulting unified diff as a patch file. >> >> 4) Submit via the project bug tracker, with notes on what the patch >> does, what branch to apply it to, how well it's been tested, etc. >> >> I think all of that applies to the current LedgerSMB workflow.> Without >> presuming to speak for the committers, the usual way a > shared-respository project accepts changes is to: > > 1) svn checkout the appropriate branch (currently active are /trunk and > /branches/1.2) > > 2) Make and test your changes to the local working copy. > > 3) svn diff and save the resulting unified diff as a patch file. > > 4) Submit via the project bug tracker, with notes on what the patch > does, what branch to apply it to, how well it's been tested, etc. > > I think all of that applies to the current LedgerSMB workflow. > > Thanks, > Jeff ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
