So the whole lockdown once you update is a ???
Seriously, if this gave us latest glibc etc I would be happy to not look back, but...

My opinion is we should push cssu as an official update so that people who don't come here learn about it and get to enjoy all those new features. Of course noone is forced to update but then again, we can have the new QT as standard and we can publish qtcomponents applications on extras without fear that half the users will never be able to use them. As more and more applications come to harmattan we have to take advantage, not make the life of developers hard.

They cant because they are not official as in "nokia" official. When I started this thread I also wondered if this was released by Nokia as an official PR how many more people would just use it and not think twice.

Good point on the harmattan apps I wonder what has been held back because of incompatibility, cutetube update was a mess over the last few days because it didn't play nice with old qt binaries

If it was Nokia official everyone would, guaranteed QA. Also a lot more would if it would allow one to revert and reinstall nokia official components when they encountered a nasty bug without flashing. Making it a one way trip scares a lot of people, especially with the amount of people reporting problems (even if 100% of them are speed/battery patchers - no way back, maybe backupmenu should make it into CSSU for a revert). Still, after freemangordon's reply I feel it is someone's decision to make it one way (applish lockdown) and not a neccesity

@szopin

QA in what respect? backwards compatability? PR 1.2 to 1.3 there were plenty of issues. How exactly do you roll back from pr 1.2 to 1.3 without reflashing? Most importantly you are comparing nokia PAID development team who also has access to change all of the closed bits to a bunch of devs who do this on the side?

btw the qt compatability issue are from qt itself made by Nokia the ones you claim did a lot of QA. Your argument is full of holes.

If one can install .debs from CSSU without breaking everything (dependencies right?) what stops uninstall script installing the stock/nokia packages when you are not happy with CSSU?
Seems like a decision taken when everyone wants portrait to tie them once they get it. Sorry, but I now seriously doubt uninstalling/reverting CSSU is such a big issue as it ismbeing sold

Since you seem to know more than the cssu team maybe you should get involved. Even better you could just take cssu, source is published, and make it removable then repackage it, if you think it is that simple.

The fixes that interest me seem so (or 2 lines of code changing one button definition and colour definition) require reflash? This thread has been hailing CSSU as a bug-fix not only portrait. As I and most of who's left are console guys, or fully landscape happy people seems that first audience of CSSU left, leaving bugs behind them. Yet people here advertise it as embracing the future (why not iphone, this is like jetpack, no?). If CSSU lovers really wonder why so many non-CSSU are left, the answer is above. Why lockdown if you can just install fixes you need/want? If bug-fix log was full people could just install newer/better debs, without bullet to the head once you install

EDIT: also some solutions like black/whitelist of applications would be less resource hungry when you apply them to CSSU .debs. Rotating when call is incoming is already lagging, checking that vs thousand of apps is not going to make it faster. Making such a list for noteworthy fixes ()properly QAed) will make life easier for all of us.

Again if it is that simple change it the source is open no one is going to stop you ...its time to put your money where your mouth is.

:$ I will gladly spend some time black/whitelisting packages compatible with 1.3.1, thkis shouldn't impact performance at least