From owner-freebsd-ports Thu May 27 18:34:52 1999 Delivered-To: freebsd-ports@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 60BBB151A9 for ; Thu, 27 May 1999 18:34:47 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id DAA04323 for freebsd-ports@freebsd.org; Fri, 28 May 1999 03:34:46 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m10n69x-000WyXC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Thu, 27 May 1999 21:49:45 +0200 (CEST) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Right way to upgrade a port Date: 27 May 1999 21:49:42 +0200 Message-ID: <7ik7km$c6l$1@mips.rhein-neckar.de> References: <19990526171236.F917@fisicc-ufm.edu> To: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oscar Bonilla wrote: > I know! I've been bitten by it in the past. That's why I was posting. > Maybe there should be an option (upgrade?) in the package/ports system > that would do both, i mean deleting the old package without worring > about dependencies and installing the new version... just a thought. Move the /var/db/pkg//+REQUIRED_BY file to a safe place, pkg_delete the port, install the new version, move +REQUIRED_BY back. Note that if the port has sufficiently changed, the other ports depending on it will then be *broken*. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de >H Deutsche Transhumanismus-Mailingliste echo 'subscribe trans-de' | mail majordomo@lists.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message