View Single Post
Posts: 805 | Thanked: 1,605 times | Joined on Feb 2010 @ Gdynia, Poland
#871
Originally Posted by joerg_rw View Post
And yet that's exactly the problem we seen with early maemo5 upgrades, like PR1.0 ->PR1.0.1 iirc
As far as I remember, the main purpose of one of the early updates (1.0->1.0.1 or 1.1->1.1.1) was to change some filesystem properties (compression?) to make bigger update (1.0.1->1.1 or 1.1.1->1.2) possible with less space available on device (please correct me if I'm wrong, it was >2 years ago, I can be wrong).

Originally Posted by Estel View Post
Binary file replacement - as suggested - is one way, but You could also grab vanilla camera-ui package, unpack it, edit control files to mimic CSSU'ish camera-ui, and pack it again - installing such version should satisfy dependencies. While it's more elegant solution than just replacing binaries, it's still dirty hack, and You will need to redo it with every update of CSSU's camera-ui (to mimic next version).
Wouldn't it be better to edit control files to mimic other package (so it won't get overwritten after each camera-ui update)? Or does Nicolai's camera-ui package replace some files used by stock camera-ui, so it would require making this operation everytime? (but it would still be easier - have this package as e.g. stock-camera-ui and just reinstall it after each camera-ui upgrade, so files would get overwritten again).

By the way, I feel highly offtopic right now
 

The Following 2 Users Say Thank You to misiak For This Useful Post: