There's one section missing from the instructions for downloading a
tarball via FTP and migrating it to cvs.
I speak, of course, of the paragraph that explains that so many files end
up missing this way that after three tries you will give up, rm -rf wine,
do a full cvs -z 3 checkout wine, and kick youself hard for not just doing
a full checkout in the first place because then you'd have had a finished
build half an hour ago.
--
Linux Now! .........Because friends don't let friends use Microsoft.
phil stracchino :: alaric@babcom.com :: halmayne@sourceforge.net
unix ronin :::: renaissance man :::: mystic zen biker geek
2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold)
Phil Stracchino wrote:> > There's one section missing from the instructions for downloading a > tarball via FTP and migrating it to cvs. > > I speak, of course, of the paragraph that explains that so many files end > up missing this way that after three tries you will give up, rm -rf wine, > do a full cvs -z 3 checkout wine, and kick youself hard for not just doing > a full checkout in the first place because then you'd have had a finished > build half an hour ago.I don't recall having this problem. Only problem I had was finding the right place to download the cvsfiles tarball. The link was broken... - Dan
On Mon, 1 Oct 2001, Phil Stracchino wrote:> There's one section missing from the instructions for downloading a > tarball via FTP and migrating it to cvs. > > I speak, of course, of the paragraph that explains that so many files end > up missing this way that after three tries you will give up, rm -rf wine, > do a full cvs -z 3 checkout wine, and kick youself hard for not just doing > a full checkout in the first place because then you'd have had a finished > build half an hour ago.You're referring to the section that says you have to use -Pd options when you cvs update? That's in "the starter's manual" (http://www.winehq.com/devstart.shtml)