From owner-freebsd-ports Wed Sep 29 11: 1:37 1999 Delivered-To: freebsd-ports@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1765E1590F; Wed, 29 Sep 1999 10:59:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0740F1CD481; Wed, 29 Sep 1999 10:59:56 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Wed, 29 Sep 1999 10:59:55 -0700 (PDT) From: Kris Kennaway To: Jeremy Lea Cc: Jonathan Chen , freebsd-ports@FreeBSD.ORG Subject: Re: glib12 deinstall failure In-Reply-To: <19990928232212.A77294@shale.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 28 Sep 1999, Jeremy Lea wrote: > Seriously. CVSup the ports collection unless you have a really good > reason not too. And install the port upgrade kit if you need it - I'm > assuming you're not running -CURRENT. The Ports collection is for > -STABLE only. If it works on -CURRENT you're just lucky (doubly lucky > since we all know -CURRENT is broken unless you happen to hit a good > build). If you're running a release, or an out of date -STABLE then you > might find that ports are broken too. I didn't think this was the case - we build packages for 4.0, so this implies that -current is supported. As I understood it, it's just -stable and -current, not -release or anything older. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message