Re: Uploading to Extras: For Fedora User?
 

mikkov:

Yes, I have confirmed that it is possible to use 'py2deb' even on binary packages like 'graphviz', but I will certainly investigate the possibility (as you suggest) of doing it a more 'normal' way. However, I will need to wrap my heard around the concept of packaging the *binaries* that I have compiled, and not the *source* of the app itself. Will this just all 'fall into place' if I go down that road?

Re: Uploading to Extras: For Fedora User?
 

When done right, running dpkg-buildpackage should build the application (run Makefiles), and package everything up correctly.

Re: Uploading to Extras: For Fedora User?
 

debian/rules files have at least 4 "stages".

configure, build, install & binary.

In configure, things like "configure" get run, which, if the program uses autotools, generates the Makefiles.

In build, the "make" command gets ran which, as you probably know, generates the binary.

In install, usually, "make install" gets ran which installs files to their right places. If not, you have to figure out how to get the file to the right place.

And in binary, this is where the debhelper does its stuff in preparing and producing the deb.

* The stages are correct but I am biased in me assuming autotools. Other build systems may be used, you'll have to make concessions then in that case. But graphviz uses autotools, so you should be ok.

It's also worth noting that free is *only* for packages with source, not to mention that providing a binary w/out the source can infringe on the terms of some licenses.

Re: Uploading to Extras: For Fedora User?
 

You can also see here:

http://repository.maemo.org/extras-d...gs_1.1_all.deb


A simple example for a debian/ directory that packages a python program and works with dpkg-buildpackage (and with the autobuilder). It can easily be used to package any files (binary or otherwise) you created by some other method.

Re: Uploading to Extras: For Fedora User?
 

Thanks again, all of you! I envy your casual approach to all this stuff. I guess that is the price I have paid for getting into app development so late in life -- the best that I can do is to use the *easiest* computer language (Python), and push 'packaging' onto the back burner as much as possible. :)