Re: Lostwages

[Jakob Eriksson]

Andreas Mohr wrote:
> > 4)Tell users of slow connections to use z9, as they probably have more processor
> > power than bandwidth.
>
> People should NOT use -z9 (we've been through this before), since it places
> an abnormally sane (normally insane? :) burden on the CVS server.

Isn't there a bug with some CVS clients or servers with the use of ANY 
-z but 0?

/Jakob

Lostwages

[Dimitrie O. Paun]

On January 3, 2004 07:42 am, Jakob Eriksson wrote:
> Isn't there a bug with some CVS clients or servers with the use of ANY
> -z but 0?

Indeed, for older CVS clients. That's why the patch points out that
you need CVS 1.11.5 or greater to use that feature.

However, I think the patch is missing the point. Using one of the
CVS servers directly is just too painfull -- the tree is too big
for that, comperssion or not (at least in my experience, and I'm
connect via a fast cable modem to the net).

We'd better explain how to setup cvsup instead. I've described my
setup sometime ago, and Brian included it as a story in WWN, if
anyone is interested... ;)

Lostwages

[Mike Hearn]

On Sat, 2004-01-03 at 17:16, Dimitrie O. Paun wrote:
> We'd better explain how to setup cvsup instead. I've described my
> setup sometime ago, and Brian included it as a story in WWN, if
> anyone is interested... ;)

I thought cvsup copied the entire repository, not just the source tree.
Wouldn't that be even more huge?

I think a useful topic at WineConf might be replacements for CVS. Just
long term thinking....

Lostwages

[Lionel Ulmer]

> I thought cvsup copied the entire repository, not just the source tree.
> Wouldn't that be even more huge?

Well, if you just use CVS to get a recent version of Wine, plain CVS is just
fine. But if you use more advanced features of CVS often (like getting
histories of files and stuff like that), having a local copy of the whole
repository may be good.

Lionel

Lostwages

[Dimitrie O. Paun]

On January 3, 2004 02:52 pm, Mike Hearn wrote:
> I thought cvsup copied the entire repository, not just the source tree.
> Wouldn't that be even more huge?

Well, initially it will be a lot more, yes, but if you plan to do
any work (cvs diff, cvs log, etc), cvsup it's a _lot_ faster/smarter
on updates. So the idea is to:
  1. Use cvsup to duplicate the entire repository on your box
     (cvsup is very smart about keeping this up to date)
  2. Check out your local copy from this private repository.

You just need to monitor the wine-cvs list (which all developers
should do anyway) for when to run cvsup to update your local repository.