Date: Sat, 9 Nov 2002 12:45:27 +0200 From: Sheldon Hearn <sheldonh@starjuice.net> To: Daniel Eischen <eischen@pcnet1.pcnet.com> Cc: current@FreeBSD.org Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021109104527.GD347@starjuice.net> In-Reply-To: <Pine.GSO.4.10.10211081806220.10745-100000@pcnet1.pcnet.com> References: <20021108.142609.112624839.imp@bsdimp.com> <Pine.GSO.4.10.10211081806220.10745-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On (2002/11/08 18:13), Daniel Eischen wrote: > > The problem is that you cannot have 4.x packages and 5.x packages > > co-mingled on the same system. that's what I'm trying to fix. You'd > > have to rebuild the 4.x packages before they are fixed. > > I don't think this is a show-stopper. Just recompile all your > ports or use the pre-built 5.0 packages. If we keep thinking only in terms of software for which source is available, we'll soon find ourselves completely estranged from commercial ventures and we can kiss any hope of serious vendor support for FreeBSD good-bye. If the final word on this whole issue is "You can't run binaries compiled for 4.x-RELEASE on 5.x-RELEASE" then we should start puckering up. Developers tend to remember these things and you don't have to screw them too many times before they remove FreeBSD downloads from their web sites and replace them with a brief message explaining that "We don't have time to cope with FreeBSD's disregard for backward compatibility." At that point, whining about how they shouldn't have been fiddling with these symbols in the first place is bound to be a fruitless exercise. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021109104527.GD347>