Date: Mon, 21 Jan 2002 23:39:23 -0500 From: Tadayuki OKADA <tadayuki@mediaone.net> To: Mikhail Teterin <mi@aldan.algebra.com> Cc: will@csociety.org, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/graphics/gd Makefile pkg-comment Message-ID: <20020121233923.75304d3c.tadayuki@mediaone.net> In-Reply-To: <200201220425.g0M4PlQ53898@aldan.algebra.com> References: <20020121232710.711cd51d.tadayuki@mediaone.net> <200201220425.g0M4PlQ53898@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 21 Jan 2002 23:25:46 -0500 (EST) Mikhail Teterin <mi@aldan.algebra.com> wrote: > On 21 Jan, Tadayuki OKADA wrote: > >> > You do know that libraries undergo source and binary incompatible > >> > changes over time, right? Did you check to make sure that your > >> > ports will not be affected by these? > >> > >> Yes -- for the foreseable future. We are talking source > >> incompatibility only, btw. If such incompatibility is introduced, it > >> will break the building of a port. This breakage will signal the need > >> for a fix. > > > You can break binary compatibility without breaking source > > compatibility. And it's not rare case. > > Would you be able to offer an example on how this is relevant to the > argument? Thanks! Sorry, I was not clear. I meant: If port A depends on port B's library. port B updated. Assume it breaks binary compatibility. port A build will not be broken, so forget PORTREVISION bump. People update port B, but not port A. so port A will stop working. > > -mi > -- Tadayuki OKADA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020121233923.75304d3c.tadayuki>