From owner-freebsd-questions Tue May 15 9:44:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 19D1F37B422 for ; Tue, 15 May 2001 09:44:52 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id LAA65061; Tue, 15 May 2001 11:44:50 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 15 May 2001 11:44:49 -0500 (CDT) From: Chris Dillon To: Cc: Subject: Re: pkg_update In-Reply-To: <01051512270602.17969@psych.ward.vt.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 May 2001, Daniel Fisher wrote: > this seems to work well. Correct me if I'm wrong, but portupgrade > will not work if you are upgrading to a port which produces a > newer shared object.. So if your current version of png is > libpng.so.4 & you compile the newest version which produces > libpng.so.5 This will break any applications which were compiled > to use libpng.so.4 Is that right? Or does portupgrade fix this as > well? I imagine it would break the old software, yes, unless the old library were backwards compatible. I have upgraded png a few times already without any problem, but I'm not sure if I did a major version upgrade at some point in time or just a minor. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message