From owner-freebsd-ports Wed Mar 20 20:51: 7 2002 Delivered-To: freebsd-ports@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.6]) by hub.freebsd.org (Postfix) with ESMTP id B4CC837B419 for ; Wed, 20 Mar 2002 20:51:01 -0800 (PST) Received: from localhost (trevor@localhost) by blues.jpj.net (8.11.6/8.11.6) with ESMTP id g2L4iPo01051; Wed, 20 Mar 2002 23:44:25 -0500 (EST) Date: Wed, 20 Mar 2002 23:44:24 -0500 (EST) From: Trevor Johnson To: Kris Kennaway Cc: "Stephen L. Palmer" , Subject: Re: XFree86-4-Server / x11/wrapper issue In-Reply-To: <20020320200527.A47591@xor.obsecurity.org> Message-ID: <20020320232352.F29954-100000@blues.jpj.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Kris Kennaway wrote: > On Wed, Mar 20, 2002 at 06:23:03PM -0600, Stephen L. Palmer wrote: > > After upgrading XFree86-4-server to 4.2.0 via ports, user accounts could > > no longer 'startx'. did 'make deinstall;make reinstall' in > > ports/x11/wrapper, which resolved issue. Should there be some type of > > dependency here to cause wrapper to update if allready installed? Hi, Stephen. I'm the maintainer of the wrapper port. Do you know specifically what was causing the problem? Also, do you know when you had installed the first time (or better yet, what revision of ports/x11/wrapper/Makefile did you have then)? I recently made some changes to the port, and I didn't test installing an X server, then installing the wrapper, then installing another X server. Maybe I didn't give enough thought to that case. > wrapper already RUN_DEPENDS on XFree86-4-server. If you use a tool > like portupgrade which handles dependencies properly when rebuilding, > this would presumably have been taken care of automatically. Can you be more specific about what's wrong with the way bsd.port.mk handles dependencies? Are any patches available (perhaps in the portmgr queue) which might improve the situation for users who don't have portupgrade? If there's no fix, maybe describing the deficiency would inspire someone to write one. :) -- Trevor Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message