On Thu, Jan 26, 2012 at 12:51 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > On Thu, 26 Jan 2012 12:15:01 -0500 > Mark Bidewell <mbidewel@xxxxxxxxx> wrote: > >> I just had a conversation which I believe sheds some light on the >> problem which a rolling release is trying to solve. The example is >> Ubuntu bu you could apply the same to Fedora/RHEL. >> >> My coworker wants to use Ubuntu LTS for development on Heroku. He >> wants the stability of an LTS, but he needs a later version of Ruby to >> run the Heroku tools. He has found that there is not supported way to >> upgrade Ruby short of recompiling Ruby or upgrading his entire system. >> Because of this he has returned to developing on OS X which handles >> the Ruby upgrade. > ...snip... > > This is the age old LTS 'use case'. > > I want: > > * A super stable platform. > > * Backporting security fixes only and tons of testing and care. > > * Minimal updates, only the backported security fixes after massive > testing. > > oh, and: > > * The very latest git head of php, python, ruby, or some other very > very specific component. > > The problem here is that these are opposite goals. And they are also > exclusive... ie, I might want the very latest php and nothing else, but > $otheruser may want stable php but the latest ruby. > > It's hard to win here. ;) > > kevin > > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel I understand the difficulty, but facilitating some degree of flexibility would be a big usability improvement. -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
