Date: Wed, 26 Jul 2000 15:12:05 -0700 From: Kent Stewart <kstewart@urx.com> To: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>, freebsd-stable@FreeBSD.ORG Subject: Re: README.TXT and RELNOTES.TXT not updated before release tag? Message-ID: <397F6235.C68E3DD6@urx.com> References: <677.964647898@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jordan K. Hubbard" wrote: > > > One thing I haven't seen is how or what do you do with ports. Do you > > rebuild in general or what? > > I'm not sure I understand the question.. It was a generic one. We now have new binary libraries and it would seem that some ports could be affected by the change from 4.0 to 4.1. There were some drastic changes to the binutils and etc. You will also have people upgrading from 2.x or 3.x to 4.0 and that brings a whole new compiler into the picture. Some ports like CodeCrusade died because the compiler was built with different options or had new defines in the header files. It had a new set of libraries and the arguments to some of them could change, which wouldn't affect statically linked codes. The arguments to the /binutils could have changed slightly. I never seemed to have any problems, with the one exception, but I spent a lot of time keeping my ports current. GNOME, which I don't use, was another one that was mentioned as one that needs to be rebuilt. The port people seemed to be keeping up in most cases but I was wondering if there was a policy on rebuilding your ports on new releases or simply letting well enough alone until you find something that is broken. Kent > > - Jordan -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?397F6235.C68E3DD6>