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]> writ
"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 rep
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?Kasper-- http://industree.org/guaka/blog
_
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/a
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:
m
