[maemo-developers] [maemo-developers] Tips for making an application installer package

[From: Luca Donaggio]

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/hildon
cp -vf $(CURDIR)/p.desktop $(CURDIR)/debian/p/usr/share/applications/hildon
mkdir -p $(CURDIR)/debian/p/usr/lib/dbus-1.0/services
cp -f $(CURDIR)/p.service $(CURDIR)/debian/p/usr/lib/dbus-1.0/services

Luca Donaggio

2006/2/22, Neil Jerram <neil at ossau.uklinux.net>:
>
> 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 at maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20060222/cfb5df30/attachment.htm