View Single Post
Posts: 393 | Thanked: 67 times | Joined on Feb 2010
#5
Thank you for your knowledgeable response.

Now I see that it would be wise to wait a bit after the new MeeGo device comes out to see what kind how many of the penetration testing applications will be ported over (stuff like Kismet and Metasploit, Easy Debian, and other 'power user' N900 software is likely very much tied to the N900 architecture).

I wonder if the N900 will continue to be the de-facto standard in power user utilities, or if development will shift to the new platform once it comes out.

I love the N900 but I wish it was more physically appealing, the form factor has many things to wish for. Personally the most physically appealing hardware I have seen is the HTC Touch Pro 2... it looks like a mini laptop, albeit gagged by awful Windows Mobile 6.1/6.5 operating system. The keyboard comes out, the screen tilts up.... If we could only get Maemo on the HTC Touch Pro 2... but that would cut out Nokia, which isn't going to happen. But one can dream...

Originally Posted by thp View Post
Yes, if they don't use any of the Hildon stuff. GTK+ dialogs also look a bit strange (no decorations) in the current MeeGo firmware image for the N900. The apps must not access Maemo-specific stuff through D-Bus services that are not available on MeeGo. Most Maemo 5 GUI apps use at least parts of Hildon (if they don't use Qt), though (things like kinetic scrolling, large buttons, the app menu, etc..) - so porting these will most likely require some changes.



That's probably the smallest issue You could either have dpkg installed in MeeGo as well (and don't forget that Harmattan aka "the first MeeGo-ish OS that comes out with the next Nokia phone" is still using DEB), and there are tools like alien which can convert between RPM and DEB. Ignoring some technical details (like scripts and dependency information amongst other metadata), packages can be though of as archive files that simply contain all files as they are installed in the file system - if the dependencies are satisfied and the binaries are compiled for the correct architecture, there's no no problem with taking the contents of a .deb package and setting it up inside an RPM-based system (that is, if you don't have the source available - otherwise you could just create a Spec File and build a "native" RPM, which is less of an issue than changing the source code and rewriting code to remove the Maemo 5 dependencies and replace them with their MeeGo equivalents).