From owner-freebsd-ports Sun Aug 23 15:12:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28954 for freebsd-ports-outgoing; Sun, 23 Aug 1998 15:12:43 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from the.oneinsane.net (gw.oneinsane.net [207.113.133.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28949 for ; Sun, 23 Aug 1998 15:12:41 -0700 (PDT) (envelope-from insane@the.oneinsane.net) Received: (from insane@localhost) by the.oneinsane.net (8.9.0/8.9.0) id PAA11468 for freebsd-ports@freebsd.org; Sun, 23 Aug 1998 15:11:56 -0700 (PDT) Message-ID: <19980823151156.A11327@oneinsane.net> Date: Sun, 23 Aug 1998 15:11:56 -0700 From: "Ron 'The Insane One' Rosson" To: freebsd-ports@FreeBSD.ORG Subject: Wierd Things in the ports Mail-Followup-To: freebsd-ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i X-Operating-System: FreeBSD the.oneinsane.net 2.2.6-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone seen things get moved around in the ports on there installs. Unable to find file and directories. This has all occured on some ports I have tried to install. Wondering if it is possible to like put a freeze on cvsup for ports when there are major changes going on. Just a curious user. Thanx Ron -- -------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void -------------------------------------------------------- It's so nice to be insane, nobody asks you to explain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message