Active Topics

 


Reply
Thread Tools
Posts: 3,428 | Thanked: 2,856 times | Joined on Jul 2008
#31
Thats just it.... dpkg-buildpackage is for source packages...

he's not building from a source .... No automake, no configure, no make. Just Binaries.
__________________
If I've helped you or you use any of my packages feel free to help me out.
-----------------------------------------------------------------------------------
Maintaining:
pyRadio - Pandora Radio on your N900, N810 or N800!
 
Posts: 1,208 | Thanked: 1,028 times | Joined on Oct 2007
#32
It's still source package even if it contains only python files.
 

The Following 3 Users Say Thank You to mikkov For This Useful Post:
Posts: 3,428 | Thanked: 2,856 times | Joined on Jul 2008
#33
Odd. Seems when I was trying it I had similar issues.. that buildpackage always wanted to run the makes and compile.. then whined when they weren't there.

ETA:

Also.. as long as the package passes Lintian checks.. why would it matter which way it was made a .deb? The format is the same..
__________________
If I've helped you or you use any of my packages feel free to help me out.
-----------------------------------------------------------------------------------
Maintaining:
pyRadio - Pandora Radio on your N900, N810 or N800!
 
Posts: 1,208 | Thanked: 1,028 times | Joined on Oct 2007
#34
buildpackage does what debian/rules says is it to do + it generates diff.gz where BrentDC is caught (+ some other things)
 

The Following 2 Users Say Thank You to mikkov For This Useful Post:
Posts: 3,428 | Thanked: 2,856 times | Joined on Jul 2008
#35
So essentially you need to modify the rules and remove all the dh_make, dh_* entries, and anything else in there that causes problems.

I see. Thanks.
__________________
If I've helped you or you use any of my packages feel free to help me out.
-----------------------------------------------------------------------------------
Maintaining:
pyRadio - Pandora Radio on your N900, N810 or N800!
 
BrentDC's Avatar
Posts: 903 | Thanked: 632 times | Joined on Apr 2008
#36
Originally Posted by mikkov View Post
yes, you should be using dpkg-buildpackage to build .debs, it might have something to do with missing icon.

I believe qwerty12 explained how to fix the problem with dpkg-buildpackage. If those instructions are not helping, I have to ask you to post the error message and maybe the whole source package here. Otherwise we are, again, just guessing
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.
__________________
-Brent

Author of TouchSearch -- web searching software for Maemo 5.

Mobile Device lineage: Palm Z22 -> Palm TX -> Nokia N800 -> Nokia N900
 
jeremiah's Avatar
Posts: 170 | Thanked: 261 times | Joined on Feb 2009 @ Gothenburg, Sweden
#37
Originally Posted by fatalsaint View Post
Only thing I don't like about the New Maintainers Guide, from what I've read, is it pretty much assumes you're dealing with a source package (.tar.gz) to be used with automake...

In this case of Python/perl things.. there is no source package. The source IS the binaries. All you need to do is make your structure, create a control/copywrite/changelog file, and make the package.

Seems it would be a bit easier than the dh_make method of doing things..
There is other documentation written regarding dynamic language support for packaging in debian.

For a source package, all you have to do is create a directory to hold your script, then you can use tar and gzip to create a tarball. Add a Makefile and you are ready to go!
 
jeremiah's Avatar
Posts: 170 | Thanked: 261 times | Joined on Feb 2009 @ Gothenburg, Sweden
#38
Originally Posted by mikkov View Post
Are you building the package with dpkg-buildpackage?

Non-related suggestions:

use "Architecture: all" since this is pure python application

with "XB-Maemo-Display-Name:" field you can get better formatted title, for example "XB-Maemo-Display-Name: Quickclip"
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. :^)
 
jeremiah's Avatar
Posts: 170 | Thanked: 261 times | Joined on Feb 2009 @ Gothenburg, Sweden
#39
Originally Posted by fatalsaint View Post
Thats just it.... dpkg-buildpackage is for source packages...

he's not building from a source .... No automake, no configure, no make. Just Binaries.
A deb package is a binary. dpkg-buildpackage builds these binary packages which have as their suffix ".deb". You can use, and should in fact use, dpkg-buildpackage to create debs.
 

The Following User Says Thank You to jeremiah For This Useful Post:
jeremiah's Avatar
Posts: 170 | Thanked: 261 times | Joined on Feb 2009 @ Gothenburg, Sweden
#40
Originally Posted by mikkov View Post
It's still source package even if it contains only python files.
Absolutely. Those files get chmoded to executables and installed. You need a debian/rules file for that and to create a debian/rules file you need a Makefile. All you need to add to your python script is the Makefile and you should be on your way.
 

The Following 2 Users Say Thank You to jeremiah For This Useful Post:
Reply

Tags
debian, packaging


 
Forum Jump


All times are GMT. The time now is 20:24.