no good with HTML so I defer to others for the markup, otherwise I'd
submit a patch:
Under "Unix":
"
To do the equivalent of a "cvs update" on the Mozilla tree you've
previously checked out, do this:
% cd mozilla
% make -f client.mk pull_all
"
Under "Windows":
"
To do the equivalent of a "cvs update" on the Mozilla tree you've
previously checked out, do this:
C:\> cd <mozilla_src_root>
C:\> nmake -f client.mak pull_all
"
Somebody else will have to fill in the "Mac" section, haven't touched
one (nee, seen one) in years.
Ian Hickson wrote:
>
> On Fri, 17 Aug 2001, JTK wrote:
> >
> > Ian Hickson wrote:
> >>
> >> On Fri, 17 Aug 2001, JTK wrote:
> >>>
> >>> I see no way to do a simple "cvs update". There's gotta be one, could somebody
> >>> please tell me how to do it? And add it to the web site?
> >>
> >> See:
> >>
> >> http://www.mozilla.org/cvs.html
> >
> > Yeah I saw that. I was able to checkout the tree, though why I couldn't
> > just do a "cvs checkout" the same way I can in all other cvs projects
> > (including GCC) still escapes me.
>
> There is a LOT of stuff in the tree, for example Bugzilla and Mozbot are
> in there. Also, a lot of the stuff is not on the HEAD but is on branches,
> to allow easier modularity and so on, for example libpr0n (the image
> library) and NSPR (the portable runtime library) are not in
> "SeamonkeyAll", if I recall correctly.
>
> > Didn't see any mention of how to do a "cvs update" (like I can in all
> > other CVS projects) though.
>
> The makefile I mentioned:
>
> cvs co mozilla/client.mak
> nmake -f client.mak pull_all
>
> ...will do it for you, including taking into account all the side files on
> different branches and so on.
>
> > Icidentally I tried to do a "cvs update" from the root and it started
> > pulling in all kinds of crazy crap that I don't think I wanted, so I
> > killed it.
>
> Now you see why we don't recommend that! :-)
>
> >> Basically, the easiest way on Windows to make sure you pull the right
> >> files is to use a batch file which does this:
> >>
> >> cvs co mozilla/client.mak
> >> nmake -f client.mak pull_all
> >
> > Right, but once they're pulled, how do I keep them synced to CVS? If I
> > do that again, I lose all my changes, right?
>
> Nope, that script just does an update. Any changes will be kept. Basically
> it does a "cvs up" in all the relevant directories, branches, and so on.
>
> HTH,
> --
> Ian Hickson )\ _. - ._.) fL
> Netscape, Standards Compliance QA /. `- ' ( `--'
> +1 650 937 6593 `- , ) - > ) \
> irc.mozilla.org:Hixie _________________________ (.' \) (.' -' __________
