Indeed, but that was only intended to be one example of where breakage can occur by living on the bleeding edge. In general, Trisquel follows the packages that exist in the corresponding upstream Ubuntu version.
"The only way that I could see this being an issue, and please correct me if
I'm wrong, is if the libraries that the package depends on are newer than
what is expected and the API has some deprecated pieces that were taken out
between revisions thus breaking programs that relied on the old style. In
this event, could you not just keep both version of the library available and
just have that specific program be compiled using the library that it
needs/wants"
- Re: [Trisquel-users] Outdated Trisquel Packages jason
- Re: [Trisquel-users] Outdated Trisquel Packages jason
- Re: [Trisquel-users] Outdated Trisquel Packages onpon4
- Re: [Trisquel-users] Outdated Trisquel Packages dev . deckardcain
- Re: [Trisquel-users] Outdated Trisquel Packages onpon4
- Re: [Trisquel-users] Outdated Trisquel Packages jason
- Re: [Trisquel-users] Outdated Trisquel Packages dev . deckardcain
- Re: [Trisquel-users] Outdated Trisquel Packages dev . deckardcain
