[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: patch attempts to apply patches/*,v
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Re: patch attempts to apply patches/*,v
- From: Hanspeter Roth <hampi_(_at_)_rootshell_(_dot_)_be>
- Date: Mon, 9 Jun 2003 23:08:40 +0200
- Mail-followup-to: ports_(_at_)_openbsd_(_dot_)_org
- Reply-to: ports_(_at_)_openbsd_(_dot_)_org
On Jun 09 at 12:44, Ben Goren spoke:
> We do. Nuke your ports tree and get a clean copy. Don't mess with
> CVSup. I've never had much luck with it, and it's always seemed a
> whole heck of a lot more complicated that it needs to be. Take a
I always used cvsup for /usr/ports. This is thought to be the
production tree. Cvsup usually works for me.
I thought I did cvs (cvs ... ports) in /usr/cvs. /usr/cvs is thought
for practicing. But now I'm surprised some files also went in
Ok. I'll install /usr/ports anew.
> Or, *far* better, use packages. There are only two situations
I want to use /usr/cvs for practicing with building ports.
Visit your host, monkey.org