Packaging Help for a Newbie Required... - Page 5 - maemo.org

Active Topics

The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 21 hrs ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 17 hrs ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 5 days, 2 hrs ago
more...

Page 5 of 5

« First

< Prev

Thread Tools

mikkov	2009-03-17 , 23:04
Posts: 1,208 \| Thanked: 1,028 times \| Joined on Oct 2007	#41

Originally Posted by jeremiah

Don't get confused by Architecture: all and Architecture: any - those are really for debian packages. Maemo has just two architectures, x86 and armel. And if your package is a based on a scripting language that can run on any architecture, it is probably best to use Architecture: any. But we are starting to get pedantic here. :^)

well basically all python packages use "all" and it's a bit stupid to generate debs for both i386 and armel when one "all" will do fine

Quote & Reply |

hns	2009-03-17 , 23:49
Posts: 87 \| Thanked: 98 times \| Joined on Oct 2007 @ Austria	#42

Originally Posted by BrentDC

I think creating a python packaging howto would be great (...)

I know I'm late to this thread, but there is actually a decent (if short) howto on python packaging for maemo in the last section of the tutorial on the pymaemo site. I used it as one of my main resources when I wrote Grumby last year (part of my motivation being in fact learning python + deb packaging).

The Grumby source tgz may also be useful as learning aid, since it's basically one python file with a lot of maemo/debian padding around. I remember looking at WordPy and other python packages for inspiration at the time.

Last edited by hns; 2009-03-18 at 06:16.

Quote & Reply |

The Following 3 Users Say Thank You to hns For This Useful Post:
BrentDC, fatalsaint, qole

	Khertan	2009-03-18 , 10:50
	Posts: 1,012 \| Thanked: 817 times \| Joined on Jul 2007 @ France	#43

http://wiki.maemo.org/Py2deb

__________________
Benoît HERVIER, Khertan
KhtEditor - Sdist_Maemo - Khweeteur - PyPackager - KhtSimpleText - KhtNotes - KhtBMA - Wleux - and more ...

Quote & Reply |

The Following User Says Thank You to Khertan For This Useful Post:
fatalsaint

	BrentDC	2009-03-18 , 14:06
	Posts: 903 \| Thanked: 632 times \| Joined on Apr 2008	#44

Originally Posted by Khertan

http://wiki.maemo.org/Py2deb

Hello Khertan!

I looked at py2deb first to get this packaged, but saw that it doesn't support pre/post-inst scripts (see bottom of the wiki post) and my package relies on these.

Is this correct?

Quote & Reply |

mikkov	2009-03-18 , 17:19
Posts: 1,208 \| Thanked: 1,028 times \| Joined on Oct 2007	#45

Originally Posted by BrentDC

One last problem: when building with dpkg-buildpackage, I get this:
Code:
dh_install: quickclip missing files (), aborting
make: *** [binary-arch] Error 1
If I comment dh_install in rules the package builds fine but is just empty (and the icon shows up in AM ).

I think I'm really close.

Thanks.

Show me the source!

(I could guess something but I won't)

Quote & Reply |

	BrentDC	2009-03-18 , 19:36
	Posts: 903 \| Thanked: 632 times \| Joined on Apr 2008	#46

Originally Posted by hns

I know I'm late to this thread, but there is actually a decent (if short) howto on python packaging for maemo in the last section of the tutorial on the pymaemo site. I used it as one of my main resources when I wrote Grumby last year (part of my motivation being in fact learning python + deb packaging).

The Grumby source tgz may also be useful as learning aid, since it's basically one python file with a lot of maemo/debian padding around. I remember looking at WordPy and other python packages for inspiration at the time.

Thank you hns, both the tutorial and Grumby source were extremely helpful. Today I was successfully able to build a .deb the "proper" way. I ended up creating a setup.py and Makefile files, and with a bit of troubleshooting, a few modifications to my rules and control files, it Just Worked (TM).

Now all that is left is figuring out the whole sign packages/gpg thing (because dpkg-buildpackage gave a few warnings about it), then just upload it to the autobuilder.

Originally Posted by mikkov