Date: 29 Jan 1997 21:12:22 -0800 From: jdp@polstra.com (John Polstra) To: freebsd-ports@freebsd.org Subject: Re: Upgrade of Mesa Message-ID: <5cpajm$1be@austin.polstra.com> References: <Pine.OSF.3.95q.970129211539.4126C-100000@gilligan.eng.umd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Why can't you just use 2.1? What's wrong with that? You could look > > for > > > and destroy any older version 12.0, 13,0, etc in the Makefile. > > > > > Sure I can create an INSTALL script to do this. > > I'll try to create a "safe install" with lots of boring questions :) > > > > By the way, why the test of the "already installed" is not performed > > before installing the files. > > It sounds strange that the error message appears after having finished > > the installation, when it tries to register it. > > Why ask questions? You know where your port installed it, just check > there, and if you find the old version libs, delete them and put the new > ones in place. Only do this on install. Please don't do this fancy crap. It'll just cause problems. Do what Satoshi suggested. Don't try to make the shared library version numbers have any relationship with the version number of the distfile. I have been there and done all that, and it's a big mistake. Follow the FreeBSD rule: if the library's interface changes (or if you think if might possibly have changed), you increment its major version number. No ifs, ands, or buts. Just do it. John Polstra, maintainer of the dynamic linker -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5cpajm$1be>