Pymacs is a package that allows both side communication beetween python and emacs-lisp. With pymacs you can use python modules in emacs-lisp, and you can write extensions for Emacs in python. It's very great since python has a very robust standard library and a very large collection of third-party modules, and now all methods from those libraries are accessible via emacs-lisp. This is the project's homepage: http://pymacs.progiciels-bpi.ca/index.html
Created attachment 42803 [details] pymacs-0.22.ebuild
Created attachment 42804 [details] Configuration for site-gentoo.el file
Hi, I looked at your ebuild. I noticed that you added RESTRICT="nomirror" to it. Is it necessary to restrict mirroring of this package? Also, it has KEYWORD="-* ~x86", but is it known to break on any other arches than x86? Except these issues the ebuild is well written and could be added to CVS immediately. Thanks in advance.
1. I've added RESTRICT='nomirror' because there is no pymacs source on gentoo mirror network yet. But there is no license restrictions to put it on gentoo mirror network. 2. I could test this ebuild only on x86 arch, and I've heard that gentoo has a keywording policy that only arch team may mark a package stable on their arch. So I've marked that pymacs has unknown behaviour on all arches but x86. But I see no obstacles for it to work on other arches because there is no low-level stuff in pymacs. If I'm wrong about gentoo policy please correct me. 3. I've also forgotten to add description to ebuild, so please add it yourself. DESCRIPTION="Pymacs is a tool that allows both-side communication beetween Python and Emacs-lisp"
All right, I removed RESTRICT and added DESCRIPTION (you have good eyes, don't you :) ). You should define RESTRICT if there is any restriction to re-distribute the software (some binary software have this kind of restriction). You correctly understand Gentoo keyword policy, but '-arch' in KEYWORDS means "this package doesn't compile on arch" or "this package doesn't work on arch". If you don't have other arch to test, just leave it blank. See Gentoo Developers Handbook http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1 and http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=5 Thanks for your contribution.
