[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    RE: wne-cvsdirs-*
From:       "Juha Hartikainen" <juha.hartikainen () kno ! fi>
Date:       2000-02-28 8:38:40
[Download RAW message or body]

> My fix for this can be downloaded from 
> ftp://lufog.dhs.org/pub/wine-cvsdirs-2000109-v.1.tar.gz
> 
> I don't know if it works (i.e. if more than just the Root files were
> broken), but please try it and let me know. 
> 
> I posted this to c.e.m.w, but so far the fixed tarbal has not made it
> to ftp.winehq.com

Well.. I updated the CVS from 9907xx version. It took a while, but now
I don't have to care of it anymore, just like most of the people probably
think here ;)

> Aside:  why not?  A working cvsdirs tarball is pretty important if you
> want new developers.  Working from a 3-week old snapshot does nobody
> any good.  Maybe you have all the developers you need? :>  I tend
> think not.   No one's tried out my tarball, so i conceede that i have
> no positive feedback about it.  on the other hand i don't have any
> negative feedback either :>

I think that it is also worth to mention at www.winehq.com that the date 
of the packets (wine-xxxxxx and wine-cvs-dirs-xxxxxx) needs to be same.

At first time when getting into this CVS thingie, I downloaded most
recent version of both. And they were not from the same date. I just
thought that maybe there is no changes for wine-cvs-dirs, because
there wasn't any new version of it. Of course things went wrong big time..

> The other option is to download the entire cvs sandbox, but really
> Juha and I don't want to mirror cvs -- we just want the 
> newest source.  

Indeed.

> The 3rd option: (after getting the broken cvsdirs-2000109-v.1.tar.gz)
> 
> cd (path-to-wine-dir)
> echo ":pserver:cvs@winehq.com:/home/wine" > Root.temp
> find . -name Root -exec cp full_path_to_wine_dir/Root.temp {} \;

Last line might be something what average (ex-)Windows coder might
NOT think at first sight ;=)

-Juha

[prev in list] [next in list] [prev in thread] [next in thread]