From owner-freebsd-ports Tue Oct 10 23:30: 7 2000 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 00F1337B502 for ; Tue, 10 Oct 2000 23:30:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA11742; Tue, 10 Oct 2000 23:30:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 10 Oct 2000 23:30:03 -0700 (PDT) Message-Id: <200010110630.XAA11742@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Doug Barton Subject: Re: ports/21882: xlock + Mesa + XFree 4 = problems Reply-To: Doug Barton Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/21882; it has been noted by GNATS. From: Doug Barton To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: Re: ports/21882: xlock + Mesa + XFree 4 = problems Date: Tue, 10 Oct 2000 23:28:40 -0700 Turns out after testing that the newer versions of the X 4 and/or Mesa ports now do the right thing in terms of deciding which libs/includes to delete when Mesa is pkg_delete'd, so this PR can be closed. FYI, it turns out that libGLU is the only bit of Mesa that's missing from X 4 that xlock needs. Too bad they left that bit out, it would make life much easier. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message