>
> The problem occurs when dealing with packages that others depend on
> like libraries, the kernel, etc. I'll give you a hypothetical synopsis:
>
> Ben is running Ubuntu Breezy Badger. However, he wants to stay on the
> bleeding edge so he adds Debian Sid repositories to his
> /etc/apt/source.list. Every day the Ubuntu update manager runs
> automatically and alerts Ben when packages exist in his list of
> repositories that are newer than those he has installed. If Debian has
> uploaded a new version of glibc that is compilied with the latest gcc
> and Ben installs this package, the newer glibc may not be binary
> compatible with the Ubuntu version of glibc. The result is that all of
> Ben's programs that rely on the Ubuntu version of glibc will not work.
>
> This is a worst case scenario but you get the idea. It could be some
> suble that breaks or something major. If one is running Ubuntu, the
> safest bet is to use repositories specifically for your particular
> version of Ubuntu. The Ubuntu backports project exists to fufill the
> needs of those who prefer not to wait 6 months for upgrades. However,
> one of the policies of backports is not to upgrade any libraries.
> Unfortunately, the Firefox package functions as a library because the
> HTML renderer, Gecko, is embedded in Firefox. Therefore, Firefox will
> not be upgraded until Dapper Drake (due in April) to avoid breaking
> programs that depend on it.
>
> -Jonathon
>
Sounds like it could be risky, then.
-- --Michael Hast (the evyl robot) I'm not picking my nose. I'm pulling things out of it.----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:17:01 EDT