Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 18 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 14 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 23 hrs ago - more...
|
2009-03-17
, 00:34
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#12
|
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..
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..
 |
|
2009-03-17
, 01:57
|
|
Posts: 903 |
Thanked: 632 times |
Joined on Apr 2008
|
#13
|
Hello Jeremiah, welcome to the community :-)
The main reason I picked the Python language to use for my program is that it's easy to use. And so far packaging via Pypackager was easy, too. But now that I want to get this thing uploaded to Extras, it has become a major hassle.
I think creating a python packaging howto would be great, especially considering a lot of newbie programmers (like myself) use this language. Those that use C, probably are already familiar with the make, build, and configure steps, so packaging probably seems a lot more logical; while to a python programmer like myself, it's basically like greek.
Originally Posted by jeremiah
I just got that website via a google of the error I received; I wasn't using it as a guide or anything, frankly I haven't been using any guide.
My first concern about the link you posted is what it says at the top;
"Warning: This article is out of date and should not be used for creating new packages."
It then goes on to point to the Debian New Maintainer's guide, which is the canonical, in fact the only reliable, guide to packaging debs. Do begin here since Maemo relies on debs being built first, then modifying the deb slightly to fit maemo.
The main reason I picked the Python language to use for my program is that it's easy to use. And so far packaging via Pypackager was easy, too. But now that I want to get this thing uploaded to Extras, it has become a major hassle.
If you are still getting errors, you can mail me at jeremiah@maemo.org and I'll see if I can help. One of my goals is to create a python packaging howto so maybe we can work on that. :^)
| The Following User Says Thank You to BrentDC For This Useful Post: | ||
|
|
2009-03-17
, 16:03
|
|
Posts: 903 |
Thanked: 632 times |
Joined on Apr 2008
|
#14
|
Originally Posted by fatalsaint
Yesterday I missed the best part -- the ETA! So today I just skipped the dpkg-buildpackage step and ran your command and it built the deb fine. Thanks! The only thing that is broken now is the icon, it doesn't show in the AM...
Not sure about your error.. but you can clean that up a little and rm -f *.ex *.EX in that debian folder. Those are example files made by the helper package in case you wanted to include something similar.. but are not required and are just bloat.
Have you tried just running:
from the directory above your quickclick directory? (and make the debian directory DEBIAN).
Just a thought, from here.
ETA:
I think part of the problem here is you are trying to follow the steps to building a debian package, from a source based package. Those steps automagically build the directory structure and everything for you, then compiled the binaries, then build the package, then lintian it.
You have done half of that yourself.. so you're starting from the middle but running the commands meant for the beginning. All you have to do is package the directory and control files you already made (with the command above, or using "fakeroot dpkg-deb --build ...") and then running lintian against it manually will tell you if anything is missing or broken.
I'm no expert at packaging.. this is all what I learned when I was messing with my own repo for Deblet.
Last edited by BrentDC; 2009-03-17 at 17:11.
|
|
2009-03-17
, 16:37
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#15
|
For icons there might be a command you need to run to update the icon cache...
gtk-update-icon-cache I think???
If that works.. what you'll want to do is include a postinst script in your debian package that runs that command. The postinst will execute, as it's name implies, after the installation of the package automatically.
Or.. might be something as simple as making sure your path is the correct path to the system icon files?
gtk-update-icon-cache I think???
If that works.. what you'll want to do is include a postinst script in your debian package that runs that command. The postinst will execute, as it's name implies, after the installation of the package automatically.
Or.. might be something as simple as making sure your path is the correct path to the system icon files?
|
|
2009-03-17
, 17:20
|
|
Posts: 903 |
Thanked: 632 times |
Joined on Apr 2008
|
#16
|
Originally Posted by fatalsaint
Actually, I was referring to the 26x26 icon that appears in the application manager; I took a png and converted it to base 64 via:
For icons there might be a command you need to run to update the icon cache...
gtk-update-icon-cache I think???
If that works.. what you'll want to do is include a postinst script in your debian package that runs that command. The postinst will execute, as it's name implies, after the installation of the package automatically.
Or.. might be something as simple as making sure your path is the correct path to the system icon files?
Code:
openssl base64 -in quick_clip.png -out quick_clip.txt
|
|
2009-03-17
, 17:37
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#17
|
Ah.. well that's a little beyond me. I have no idea 
. Never done icons for App Manager.
. Never done icons for App Manager.
 |
|
2009-03-17
, 18:09
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#18
|
I know that Khertan's PyPackager does the icon conversion; perhaps you can peek into his code to see how he does it?
Oh, and while you're there, are you interested in updating it? I've got a few feature requests...
Oh, and while you're there, are you interested in updating it? I've got a few feature requests...
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
 |
|
2009-03-17
, 18:15
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#19
|
Originally Posted by BrentDC
base64 <image> also works.
I copied that text into my control file, into the XB-Maemo-Icon-26: field (making sure that I put a space in front of each newline), but it doesn't show up. I think I did everything correctly...(I used openssl instead of uuencode because uuencode wasn't installed in either Ubuntu or Scratchbox).
__________________
Ryan Abel
Ryan Abel
|
|
2009-03-17
, 18:30
|
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#20
|
Originally Posted by BrentDC
You should post your problematic control file here. Otherwise this is just guesswork.
I copied that text into my control file, into the XB-Maemo-Icon-26: field (making sure that I put a space in front of each newline), but it doesn't show up. I think I did everything correctly...(I used openssl instead of uuencode because uuencode wasn't installed in either Ubuntu or Scratchbox).
Last edited by mikkov; 2009-03-17 at 19:34.
| The Following 3 Users Say Thank You to mikkov For This Useful Post: | ||
"Warning: This article is out of date and should not be used for creating new packages."
It then goes on to point to the Debian New Maintainer's guide, which is the canonical, in fact the only reliable, guide to packaging debs. Do begin here since Maemo relies on debs being built first, then modifying the deb slightly to fit maemo.
If you are still getting errors, you can mail me at jeremiah@maemo.org and I'll see if I can help. One of my goals is to create a python packaging howto so maybe we can work on that. :^)
Regards,
Jeremiah