Re: [maemo-developers] Tips for making an application installer package
I have also developed a couple of scripts for converting debian arm packages and zaurus ipk packages to maemo packages. http://maemotalk.feelslikeburning.com/2006/02/21/maemo-package-management-tools/ ubergEEkOn 3/9/06, Neil Jerram [EMAIL PROTECTED] wrote: Kasper Souren [EMAIL PROTECTED] writes: Does anyone have a similar method for Python? I*d like to create a package for MaemoDict. And, would it be okay to include dictd in the package, or is it better to point people to the official Debian arm package?(With apologies for the late reply...)IMO relying on official Debian arm packages is a poor substitute for a proper 770 application installer package.I'd like to minimize theactions I take that require root.(On the other hand, if an official arm package had (i) no postinst orprerm scripts, and (ii) no internal hardcoding of its install location, and (iii) no dependencies except maemo, it should JustWork as a 770 package.Someone who knows dpkg-deb could probablywrite a script to check (i) and (ii), and fix up (iii), such that a 770 package could sometimes be created automatically from an officialarm package.)Neil___maemo-developers mailing list maemo-developers@maemo.orghttps://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Tips for making an application installer package
Kasper Souren [EMAIL PROTECTED] writes: Does anyone have a similar method for Python? I*d like to create a package for MaemoDict. And, would it be okay to include dictd in the package, or is it better to point people to the official Debian arm package? (With apologies for the late reply...) IMO relying on official Debian arm packages is a poor substitute for a proper 770 application installer package. I'd like to minimize the actions I take that require root. (On the other hand, if an official arm package had (i) no postinst or prerm scripts, and (ii) no internal hardcoding of its install location, and (iii) no dependencies except maemo, it should Just Work as a 770 package. Someone who knows dpkg-deb could probably write a script to check (i) and (ii), and fix up (iii), such that a 770 package could sometimes be created automatically from an official arm package.) Neil ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Tips for making an application installer package
Through somewhat painful trial and error, I've discovered that the most effective way to make a package from a standard source tarball (which uses autoconf) is to: - configure with --prefix=/var/lib/install/usr - add the following lines to debian/rules after the $(MAKE) install line: mv $(CURDIR)/debian/p/var/lib/install/* $(CURDIR)/debian/p/ rm -rf $(CURDIR)/debian/p/var (where p is replaced by the package name). This method means that the installed files correctly reference /var/lib/install where they need to (e.g. config files, shell scripts, libtool .la files), but that the .deb contains files whose names don't include the leading /var/lib/install - which appears to be what the application installer requires. Has anyone else reached the same or a different conclusion? Are these tips already documented anywhere? Regards, Neil ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Tips for making an application installer package
Yes, I do the same thing.Moreover, if your project doesn't orginally contain .service and .desktop files you should manually create theme somewhere in your source dir and add these lines to debian/rules (and create p.links accordingly to the Wiki, of course):mkdir -p $(CURDIR)/debian/p/usr/share/applications/hildoncp -vf $(CURDIR)/p.desktop $(CURDIR)/debian/p/usr/share/applications/hildonmkdir -p $(CURDIR)/debian/p/usr/lib/dbus- 1.0/servicescp -f $(CURDIR)/p.service $(CURDIR)/debian/p/usr/lib/dbus-1.0/servicesLuca Donaggio2006/2/22, Neil Jerram [EMAIL PROTECTED] :Through somewhat painful trial and error, I've discovered that themost effective way to make a package from a standard source tarball (which uses autoconf) is to:- configure with --prefix=/var/lib/install/usr- add the following lines to debian/rules after the $(MAKE) installline:mv $(CURDIR)/debian/p/var/lib/install/* $(CURDIR)/debian/p/ rm -rf $(CURDIR)/debian/p/var(where p is replaced by the package name).This method means that the installed files correctly reference/var/lib/install where they need to (e.g. config files, shell scripts, libtool .la files), but that the .deb contains files whose names don'tinclude the leading /var/lib/install - which appears to be what theapplication installer requires.Has anyone else reached the same or a different conclusion?Are these tips already documented anywhere?Regards,Neil___maemo-developers mailing listmaemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
