I have also developed a couple of scripts for converting debian arm packages and zaurus ipk packages to maemo packages. <br><br><a href="http://maemotalk.feelslikeburning.com/2006/02/21/maemo-package-management-tools/">http://maemotalk.feelslikeburning.com/2006/02/21/maemo-package-management-tools/
</a><br><br>ubergEEk<br><br><div><span class="gmail_quote">On 3/9/06, <b class="gmail_sendername">Neil Jerram</b> <<a href="mailto:neil@ossau.uklinux.net">neil@ossau.uklinux.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Kasper Souren" <<a href="mailto:kasper.souren@gmail.com">kasper.souren@gmail.com</a>> writes:<br><br>> Does anyone have a similar method for Python?<br>> I*d like to create a package for MaemoDict.<br>
> And, would it be okay to include dictd in the package, or is it better to<br>> point people to the official Debian arm package?<br><br>(With apologies for the late reply...)<br><br>IMO relying on official Debian arm packages is a poor substitute for a
<br>proper 770 application installer package. I'd like to minimize the<br>actions I take that require root.<br><br>(On the other hand, if an official arm package had (i) no postinst or<br>prerm scripts, and (ii) no internal hardcoding of its install
<br>location, and (iii) no dependencies except "maemo", it should Just<br>Work as a 770 package. Someone who knows dpkg-deb could probably<br>write a script to check (i) and (ii), and fix up (iii), such that a<br>
770 package could sometimes be created automatically from an official<br>arm package.)<br><br> Neil<br><br>_______________________________________________<br>maemo-developers mailing list<br><a href="mailto:maemo-developers@maemo.org">
maemo-developers@maemo.org</a><br><a href="https://maemo.org/mailman/listinfo/maemo-developers">https://maemo.org/mailman/listinfo/maemo-developers</a><br></blockquote></div><br>