Re: LiveUser initial commit

I think it should be in a folder Perm_LiveUser, unless you have class called Perm? - the CVS tree is supposed to be flat, so if we did have other Perm classes, then they would go in Perm_anotherone.. Anyway I could be wrong - but I thought that was the idea (sorry about that, looks like you where having enough problems with WinCVS) Quick CVS command line overview.. - as available as part of cygwin (It's not really that bad, theres on 5 commands you really need to know) cd /wherever my cvs tree is cvs -d :pserver:myname@cvs.php.net:/repository co pear/Perm_LiveUser cvs add NewFile.php cvs add NewDir cvs update -d -P cvs diff -u NewFile.php cvs commit -m 'I've updated something' NewFile.php 98% of the time, thats all you need to know. A few suggestions - no idea where they come from, but I picked them up over time.. run php -l (lint test) before you commit if you havent tested it.. always diff before you commit - makes sure that you dont accidentilly it's usually better to commit changes one file at a time - so you describe the changes in more detail, that relate to each file. Add files In small batches - avoid doing cvs add *, you usually end up adding the wrong files.. I've given up using softlinks to CVS folders on pear - it causes more trouble than it solves.. I just use a quick install script to update the application/pear directory after editing a package file.. Install script.. #!/bin/sh pear package pear install -f DB_DataObject-0.3.tgz anyway - dont fear the power of the command line :) regards alan Markus Wolff wrote:

Hi there, thanks to Rasmus, I finally got my CVS account and have committed an initial version of LiveUser to the repository. As discussed earlier, I´ve created a new top-level category "Perm" for that, so the package is now under "Perm/LiveUser". If there are objections, we can still relocate it to a more appropriate place (which I can´t think of right now). The current version reflects the work that Lukas has made on the class since I put the last version online. He added an MDB backend and lots of new features. I haven´t tested any of them yet, so it´s very likely that MDB is the only working backend at the moment, as the other two haven´t been updated with the new features yet. Due to problems with WinCVS, the example scripts are still missing in CVS. I have asked Lukas to upload them for me. Dunno why WinCVS won´t let me commit these two files - does anyone know a good alternative to WinCVS? And please don´t say commandline... Regards, Markus