An ebuild for PyBison: PyBison is a Python binding to the Bison (yacc) and Flex (lex) parser-generator utilities. It allows parsers to be quickly and easily developed as Python class declarations, and for these parsers to take advantage of the fast and powerful C-based Bison/Flex. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 62681 [details] pybison-0.1.8.ebuild suggest category dev-python.
Please fix the following and reopen: * Your indenting in DEPEND is weird. * If you have more than one die in a function, it's usually best to include a short message with each one so that we can easily tell which die has been triggered.
Created attachment 66508 [details, diff] Fixed issues of style described by ciaranm I considered also adding an einfo to inform users that they should import "bison" rather than "pybison" in programs wishing to use this module. Should this be done or is it not necessary?
(In reply to comment #3) > Created an attachment (id=66508) [edit] > Fixed issues of style described by ciaranm Thanks - I've reopened the bug as requested by ciaranm. > I considered also adding an einfo to inform users that they should import > "bison" rather than "pybison" in programs wishing to use this module. > > Should this be done or is it not necessary? It certainly wouldn't hurt, but I'd guess that folks using this module would need to (and be happy to) dig into the README and documentation listed therein. Assuming they built with the -doc flag, of course!
(In reply to comment #4) > (In reply to comment #3) > > Created an attachment (id=66508) [edit] [edit] > > Fixed issues of style described by ciaranm > Thanks - I've reopened the bug as requested by ciaranm. Sorry - didn't mean to step on your toes. Just looking for nice easy bugs to fix whilst I get the hang of "ebuilding" :-)
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Created an attachment (id=66508) [edit] [edit] [edit] > > > Fixed issues of style described by ciaranm > > Thanks - I've reopened the bug as requested by ciaranm. > > Sorry - didn't mean to step on your toes. Just looking > for nice easy bugs to fix whilst I get the hang of > "ebuilding" :-) Don't apologise - it's a help! When creating patches, however, creating unified diffs is preferable. Basically this means passing the -u switch to diff. See http://www.kegel.com/academy/opensource.html#patches for full instructions...
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
New homepage: http://freenet.mcnabhosting.com/python/pybison/ Given the fact that there wasn't any release since 2005 and the tarballs are not available anymore, I'm going to close this bug.
