Date: Thu, 31 May 2001 03:26:02 +0200 From: "Siegbert Baude" <Siegbert.Baude@gmx.de> To: <freebsd-questions@freebsd.org> Subject: Re: cvsup-bin outdated? Message-ID: <016001c0e970$a7f90e20$4011a8c0@wohnheim.uniulm.de> References: <20010528104333.A23033@dinjo.touchtunes.com> <3B1275AC.63094B90@ohio.com> <3B128D53.AEFFD9EA@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
I just got an answer from John on the stable list. So for the sake of complete archives, I paste his words now: > Is the cvsup-bin port now obsolete? It is obsolescent. I am waiting for the new cvsup and cvsup-devel packages to appear on the FTP sites. Once the new packages are available I will delete the cvsup-bin and cvsupd-bin ports. > Is the cvsup package, which is mentioned in your workaround, thought > as a replacement for the cvsup-bin port? Yes. > Do they have the same features, purpose, Yes. > size,...? Not the same, but close enough. > Is it possible, that the users, who are still using cvsup-bin, will face > problems similar to the jakarta-tomcat one in the future? Yes, although I surely hope not. :-( Users should upgrade, preferably to the cvsup-devel port, which has many bug fixes that aren't present in the other ports. > And just for my personal interest: What is the problem with the > cvsup-bin port, that it won't be patched? It is a binary, and binaries are difficult to patch. I could produce an entirely new binary, but there's no point to that since I have made the cvsup and cvsup-devel packages stand-alone now. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?016001c0e970$a7f90e20$4011a8c0>