Re: Upgrading to 7.0 - stupid requirements

On Fri, Feb 29, 2008 at 01:03:31AM +0100, Kris Kennaway wrote:
Edwin Groothuis wrote:
On Fri, Feb 29, 2008 at 12:08:22AM +0100, Marko Lerota wrote:
In http://www.freebsd.org/releases/7.0R/announce.html says

Updating Existing Systems

An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
a major version upgrade, so no matter which method you use to update
an older system you should reinstall any ports you have installed on

Should, not must. Use misc/compat6x if you don't want to do this,
but that doesn't work for things which look in the kernel (sysutils/lsof
for example)

No: must, not should.

If you don't do this, then when you update e.g. only some of the gnome
libraries without recompiling all of gnome, then your gnome binaries
will have libraries linked to libc.so.6 and libc.so.7, and to
libkse.so.2 as well as libthr.so.3, and this is a guaranteed runtime
crash because these are mutually inconsistent sets of libraries.

He wanted independance of the base OS and the installed software.
He didn't want to upgrade his software because of software version
incompatibilies.

That was the scenario where this advice was given on.

Edwin

--
Edwin Groothuis | Personal website: http://www.mavetju.org
edwin@xxxxxxxxxxx | Weblog: http://www.mavetju.org/weblog/
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Firefox on -current dumps core.
    ... When I upgraded about two weeks ago, a lot of programs dumped core. ... Upgrade all the packages from source before I cvsup to -current, ... the only way to fix these problems is to rebuild all your ports in order that the installed ports match your library set and that all applications linked against old library versions are updated. ... Eventually, there will be a compat6x port that installs compatibility versions of libraries, but there are a number of open questions about how we want to approach that so the short term solution of upgrading everything is the way to go. ...
    (freebsd-current)
  • upgrading gnome
    ... updated your ports tree? ... GNOME has been updated to 2.16. ... upgrade your GNOME desktop or/and other applications ... and building it from the ports tree.. ...
    (freebsd-questions)
  • Re: Firefox on -current dumps core.
    ... When I upgraded about two weeks ago, a lot of programs dumped core. ... Upgrade all the packages from source before I cvsup to ... the only way to fix these problems is to rebuild all your ports in order that the installed ports match your library set and that all applications linked against old library versions are updated. ... Eventually, there will be a compat6x port that installs compatibility versions of libraries, but there are a number of open questions about how we want to approach that so the short term solution of upgrading everything is the way to go. ...
    (freebsd-current)
  • Major Error Upgrading to GNOME 2.12
    ... I CVSup'd the ports tree and prepared to run ... I noticed a large number of GNOME ports in my output from ... upgrade script to upgrade to 2.12. ... Note that I failed to use the restart ...
    (freebsd-questions)
  • Re: SOLVED: qemu: freebsd6_mmap -1 errno 12 Cannot allocate memory
    ... You will have applications you are using linked against FreeBSD libraries that no longer have any FreeBSD security team support. ... misc/compat3x is marked as Forbidden / Ignore in the ports tree due to an unfixed security bug that isn't going to be fixed. ... Some of the ports that have got security related updates are fairly key libraries such as OpenSSL. ... As soon as you need to upgrade one dependency based on an older release, you have a potentially complex problem on your hands, especially as the ports tree no longer supports 4.x or earlier. ...
    (freebsd-stable)