Re: Compiled pyton files for all arch?

Rob Tillotson <[EMAIL PROTECTED]> writes: > If your package contains only Python code, you can then safely make it > Architecture: any. Er, I meant "all". Sorry. :) --Rob -- Rob Tillotson N9MTB <[EMAIL PROTECTED]>

Re: Compiled pyton files for all arch?

opy the appropriate snippet from the postinst and prerm of one of them. If your package contains only Python code, you can then safely make it Architecture: any. --Rob -- Rob Tillotson N9MTB <[EMAIL PROTECTED]>

Re: Compiled pyton files for all arch?

Rob Tillotson <[EMAIL PROTECTED]> writes: > If your package contains only Python code, you can then safely make it > Architecture: any. Er, I meant "all". Sorry. :) --Rob -- Rob Tillotson N9MTB <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL

Re: Compiled pyton files for all arch?

st copy the appropriate snippet from the postinst and prerm of one of them. If your package contains only Python code, you can then safely make it Architecture: any. --Rob -- Rob Tillotson N9MTB <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: getting a python module accepted by python?

are in it, because I never have to look. ;-) > Also, sorry to get off topic, but should the postinst compile the > module? Yes. > Won't this happen the first time the module is imported? Only if the user has permissions to write the .pyc/.pyo file, which he won't if he is non-roo

Re: getting a python module accepted by python?

are in it, because I never have to look. ;-) > Also, sorry to get off topic, but should the postinst compile the > module? Yes. > Won't this happen the first time the module is imported? Only if the user has permissions to write the .pyc/.pyo file, which he won't if he is non-roo

Re: getting a python module accepted by python?

a different place in the naming hierarchy may break other code that uses it. In this case, this means you should just put soaplib.py in the site-packages directory -- since it stands alone, or at least it did last time I looked at it, there is no need to do anything more complicated than that. --Rob -- Rob Tillotson N9MTB <[EMAIL PROTECTED]>

Re: getting a python module accepted by python?

a different place in the naming hierarchy may break other code that uses it. In this case, this means you should just put soaplib.py in the site-packages directory -- since it stands alone, or at least it did last time I looked at it, there is no need to do anything more complicated than that.

Re: how to package python module as shared lib??

intain have Python C modules in them, and are fairly simple. For example, see: python-kjbuckets, python-mxstack, python-mxtools, python-mxdatetime, or for larger examples python-xml or pyrite. --Rob -- Rob Tillotson N9MTB <[EMAIL PROTECTED]>

Re: Questions about packaging a python script

ves.) There is also a mailing list, debian-python, which is supposed to be used for discussion of future Python policy, eg. the transition to FHS, but it hasn't actually gotten any traffic yet. If you're interested in the topic, feel free to subscribe and help out. --Rob -- Rob Tillotson N9MTB <[EMAIL PROTECTED]>

Re: Questions about packaging a python script

mailing list? It hasn't gotten any traffic yet that I know of, but I gather it is supposed to be used for discussing Python-related stuff... - --Rob - -- Rob Tillotson N9MTB <[EMAIL PROTECTED]> -BEGIN PGP SIGNATURE- Version: 2.6.3a C

Re: Copyrighting..

commended method is to insert a bit of boilerplate in each source file, and supply a copy of the GPL in the distribution. (If you are making a Debian package, of course, you don't have to do the latter; merely refer to the existing copy in /usr/doc/copyright.) --Rob --

Re: New Package - heyu, need guidance

also want to add a [EMAIL PROTECTED] user ID to your key so that you can use that address in your packages. Enjoy, --Rob -- Rob Tillotson N9MTBInternet: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

library questions

idea is to have 'objpak1' and 'objpak-gcc1'... on the other hand, I could use 'objpak-poc1' and 'objpak1'. Have there been any policy decisions on this sort of thing? Is there a better solution? Does it even matter, since hardly anyone uses Obj

my first package... loads of questions :)

ones first :) - --Rob - -- Rob Tillotson N9MTBInternet: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface iQCVAwUBNVyvA3R+ngWruQ4VAQF5iAP/Z45UEc5LgHJSFLjJ5fFpZO4xtjo5gYBV S

Re: Example package

debhelper (which is apparently the preferred thing to use now) to do the hard work :) Using deb-make, it took me about five minutes to make a basic binary package... deb-make, edit a couple of files, fix the makefile to install stuff in the right place, su, and 'build&#