From owner-freebsd-x11@FreeBSD.ORG Sat Oct 13 14:05:28 2007 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A69F16A417 for ; Sat, 13 Oct 2007 14:05:28 +0000 (UTC) (envelope-from greg@ltcc.com) Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by mx1.freebsd.org (Postfix) with ESMTP id 34AAD13C44B for ; Sat, 13 Oct 2007 14:05:28 +0000 (UTC) (envelope-from greg@ltcc.com) Received: from [192.168.1.100] (cpe-66-65-47-70.nyc.res.rr.com [66.65.47.70]) by m1.imap-partners.net (MOS 3.8.4-GA) with ESMTP id AFN80492 (AUTH via LOGINBEFORESMTP); Sat, 13 Oct 2007 07:05:23 -0700 (PDT) From: User & Robinson Organization: Lusrosol To: Peter Jeremy Date: Sat, 13 Oct 2007 10:06:40 -0400 User-Agent: KMail/1.9.4 References: <20071012210313.GA93545@turion.vk2pj.dyndns.org> <200710122235.l9CMZ4QV008472@ms-smtp-01.rdc-nyc.rr.com> <20071013004846.GF93545@turion.vk2pj.dyndns.org> In-Reply-To: <20071013004846.GF93545@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710131006.40494.greg@ltcc.com> Cc: freebsd-x11@freebsd.org Subject: Re: "Makefile", line 85: Could not find/usr/ports/x11/xorg-clients/../../x11-servers/xorg-server/Makefi le.inc X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2007 14:05:28 -0000 On Friday 12 October 2007 20:48, Peter Jeremy wrote: > [Please don't top-post] Ugh, spending too many years with Outlook, sorry. > > On 2007-Oct-12 18:35:04 -0400, Greg Robinson wrote: > >Yes, I suspect you are correct, I am fussing with portmanager & > > portsupgrade as two apps to reestablish a clean ports environment. > > portmanager & portupgrade are functionally equivalent. Trying to use > both is likely to cause confusion both for you and the tools - you would > be better off settling on one. I did not realize that, (perhaps I'm not reading the manual carefully) This snippit of information makes my observations easier to understand. I will re-approach ports install and usage with a new frame of reference. > > >Thus far I have not found the correct sequence of commands to get ports > >clean. > > I'm not sure about portmanager but portupgrade is only intended to > manage installed ports, not the ports tree itself. You should use > something like portsnap to manage the ports tree. > > portsnap may be able to recover your ports tree but if you are in doubt, > you could delete the ports tree and start from scratch (or a -RELEASE CD) > and re-run portsnap. > Yes, exactly what I did. > If you problem is the installed ports themselves, judicious use of pkgdb > (if you use portupgrade) can probably resolve the problem. If not, a > more detailed description of the problem should elicit some assistance > here. Just before this email was read - I did exactly that. Now begins the process of making everything "current" if that is the right term.