View Single Post
Posts: 805 | Thanked: 1,605 times | Joined on Feb 2010 @ Gdynia, Poland
#79
Originally Posted by Android_808 View Post
great news aapo but i have a couple of questions.

is hal really necessary though? if we (maemo5) are only using it to automount hotplugged devices, udev+udisks would be sufficient. to use old software maybe but are you risking recreating the whole fork/cross version situation we have already.
Really? I thought it was used for more stuff... Is it really only used for automounting hotplugged devices? If so, this looks like a massive overkill...

Originally Posted by Android_808 View Post
bme/mce: are those links the same as the replacements were using/got available on maemo5? i thought ours were RE'd.
One of the links Aapo wrote (bme-rx-51 one) is the replacement availabe on Maemo5 via cssu(-devel?). AFAIK the replacement was heavily based on the Harmattan open-source version, but you are right that some parts indeed had to be reverse engineered (however, unless my memories are wrong, these were only some parts of it, not the whole bme/mce...).

EDIT:
Originally Posted by AapoRantalainen View Post
I quickly check that is has some tough dependency (I don't yet know where to get)
osso-systemui-modechange-dev
libdevlock-dev
osso-systemui-devlock-dev
osso-systemui-splashscreen-dev
libcal-dev (binary version from this can be installed from NOKIA-binaries)
I'm not sure about the other ones, but I think dropping osso-systemui-splashscreen-dev as a dependency should be safe... The package osso-systemui-splashscreen only displays Nokia logo when phone is shutting down (see file /etc/event.replace.d/osso-systemui-splashscreen - it starts splash display on stopping of dbus or dbus-actdead services) Even if the /usr/lib/systemui/libystemuiplugin_splashscreen.so file in that package needs to provide some functionality, my guess is it should be safe to make a dummy .so file which does nothing (but again, this is software we're talking, so some dumb design flaw may have caused this file to do something important...).

EDIT2:
By the way, Aapo, have you read this thread: http://talk.maemo.org/showthread.php?t=82641 ? I don't want to sound like a douche telling you what to do, but it could be a nice idea to drop all the unneded packages at first stages of your project and not spend too much time on trying to get them working (this is just an idea to consider).

EDIT3:
I have used this link a million times, but maybe I will post it once again, maybe it will be usefull (a.d. your note about using libclutter in specific version): http://linuxtesting.org/compatibilit...at_report.html - it can help detecting which versions of software can be easily used in newer versions (e.g. from Jessie). See e.g. list of possible incompatibilities with newer versions of libc, libexif, libexempi, libglib... libncurses - funny thing is this one is supposed to be in the same version in Fremantle and Harmattan, but they are incompatible somehow... Also, when some libraries reach 1.x state, they sometimes change name in debian (e.g. ssl 0.9.8 is "libssl" and 1.0 is "libssl1" - this is the example that came to my head instantly when you wrote about clutter). I remember seeing (I think on the same server) a comparison of base-system packages compatibility between different version of Debian... that could also be useful here (so you could compare compatibility and then make a decision from which source you would like to build packages for this Jessie-based Maemo).

Last edited by misiak; 2014-06-14 at 23:10.
 

The Following User Says Thank You to misiak For This Useful Post: