> But how did you dtermine the time to be 10:30:00? How do you know?
As commented above, I know 10:30 is a good time because I know that, some minutes before that, is when one script running in one of the moodle.org servers uses to update the "(Build: xxxxx)" info in version.php files. Not because 10:30 is something worlwide accepted nor anything else, but because it the time we execute that script in our servers. Just use that time because it's the "good one" for Moodle cvs. Simply that.> Is there a way that does not require "inside knowledge" of time? For example, a cvs command that can use the file versions in the manifest?
Well, in the manifest, there is a complete list of files and versions. I think you can read that file and then, request all those files individually. But I think it'll be really slow. Something like:
cvs update -r version file
executed for each line in the manifest should do the work. But you'll get 99.99% the same files with the strategy commented in my previous post.> Now my simple question: If my local copy is 1.9.1 and I want 1.9.2, do I use (1) or (2)?
Once you execute something like:
cvs update -dPr MOODLE_19_STABLE
your local copy of the cvs server
will continue operating in the MOODLE_19_STABLE branch. You don't need to specify the "-r MOODLE_19_STABLE" for each cvs command at all.
You only need to specify the -r tag if you want to change to another branch so, for example, if you want to start working with Moodle 1.7 you'll execute:
cvs update -dPr MOODLE_17_STABLE
and, once again, all the following cvs commands in that directory will operate in the MOODLE_17_STABLE branch by default.
Finally, note that each MOODLE_XX_STABLE branch "contains" all the Moodle XX versions, so, if you want to switch from Moodle 1.9.1 to Moodle 1.9.3 you don't need to change any branch, both are contained in the MOODLE_19_STABLE branch. And one simple cvs update -dP will update you to the latest code available in the branch (that right now is 1.9.2+ and will be 1.9.3 in some days... and 1.9.4 later... and...).> Sorry for such primitive question, but unfortunately documentation never explain if 1.9.2 is "new version" or "same version" relative to 1.9.1.
Is new version, but same (MOODLE_19_STABLE) branch.
NP at all! I remember my first days with CVS, branches, revisions and so on and those were difficult days!
P.S.: Finally note that all this complexity is about to get some past weekly builds. There you need the dates (with the 10:30 trick) because there is nothing else in the cvs server identifying those weeklies. But if you want releases (not weeklies) you can use the MOODLE_XYZ tags (1.9.2 = "cvs update -dPr MOODLE_192"). But IMO
you shouldn't be using releases but weeklies that include fixes for a bunch of bugs present in releases. So perhaps it's better if you forget this last paragraph after all.