From http://www.reportlab.org/pyrxp.html : ------ ReportLab are proud to present pyRXP version 0.9, the fastest validating XML parser available for Python, and quite possibly anywhere :-). RXP is a very fast validating XML parser written by Richard Tobin of the University of Edinburgh. It complies fully with the W3C test suites (although we have compiled it without Unicode support for the time being). ------ It could go in dev-python/pyrxp and I think it depends only on virtual/python Matteo Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 24445 [details] pyrxp-0.9.ebuild (New Package)
Created attachment 28399 [details] pyRXP-0.9.ebuild i've done some corrections. note that package name is pyRXP, not pyrxp.
How about installing the magical xmlutils.py too? Below are a few lines that when added to src_install() will do this, I'm sure there is a better way. And my preference is with all lower-case ebuild names. Chris distutils_python_version # sets PYVER/PYVER_MAJOR/PYVER_MINOR PYTHON_VERSION="${PYVER_MAJOR}.${PYVER_MINOR}" insinto /usr/lib/python${PYTHON_VERSION}/site-packages/ doins ${S}/examples/xmlutils.py
examples are installed in /usr/share/doc/pyRXP-<version>/examples.
Reassigned to maintainer-wanted.
Created attachment 82752 [details] pyRXP-1.07.ebuild Modified the 0.9 ebuild to install 1.07. The source archive is created on a daily basis, and the creation date is reflected in the directory structure; the main change was getting this to work in the ebuild.
Lates pyRXP ebuild seems to emerge perfectly with pyRXP-1.12 on amd64.
(this is an automated message based on filtering criteria that matched this bug) Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accomendate you on a timely manor. 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
(In reply to comment #7) > Lates pyRXP ebuild seems to emerge perfectly with pyRXP-1.12 on amd64. > I've re-worked this for pyRXP 1.13 and it works fine on amd64.
Created attachment 181098 [details] pyRXP version 1.13 ebuild
Added in sunrise overlay you can find it at: http://overlays.gentoo.org/proj/sunrise/browser/sunrise/dev-python/pyRXP i just updated ebuild to a live ebuild because download a daily snapshot as tarball is made, i was more appropriated (and maintainable) to updated it to a live ebuild.
(In reply to Romain Perier (RETIRED) from comment #11) > Added in sunrise overlay you can find it at: > http://overlays.gentoo.org/proj/sunrise/browser/sunrise/dev-python/pyRXP > i just updated ebuild to a live ebuild because download a daily snapshot as > tarball is made, i was more appropriated (and maintainable) to updated it to > a live ebuild. because i don't know where the sunrise guys tracks their bugs i add this here: since pyRXP isn't longer a subversion repo on the company's website this ebuild doesn't work anymore. The source is now a mercurial repo hosted at bitbucket: https://bitbucket.org/rptlab/pyrxp (as one can check on their website: http://www.reportlab.com/software/opensource/)
Hello, everyone. It seems that at least one ebuild related to this bug exists in the Sunrise overlay at the moment. However, I have to regretfully announce that after a long inactivity period the Sunrise project has been discontinued and the related overlay will be eventually removed. For this reason, I'd like to ask you to reevaluate the ebuilds and consider moving them. If you'd like to maintain a package from Sunrise in Gentoo, please take a look at our Proxy Maintainers [1] project. Please make sure to take ebuilds from the unreviewed developer Sunrise repository [2] rather than the -reviewed one, since the latter has not been updated for over a year. While at it, please note that: 1. Adding a package to Gentoo requires declaring yourself as an active maintainer for it. All bugs regarding the package will be assigned to you, and you will be expected to maintain it. 2. Some packages may not be suitable for addition anymore. While there's no strong rules that would prevent you from adding a package, it may be a bad idea to add old-unmaintained packages that will shortly result in a large number of bugs reported with no solution. If that is the case, please close the bug as RESOLVED/OBSOLETE to make it easier to find packages worth adding. 3. Some of the bugs were already closed as WONTFIX/OBSOLETE/... while the relevant ebuild was kept in Sunrise. If you disagree with the original decision, you still can add the ebuild via proxy-maint. 4. Pleaes note that many of the Sunrise ebuilds are old and may be buggy. If you decide to move them, please make sure to update/clean them up. The proxy-maint team will also review your ebuilds, therefore making sure they land in Gentoo in good quality. Once again, thank you for your contribution. We hope that you will still want to contribute to Gentoo, through proxy-maint or otherwise. [1]:https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers [2]:https://gitweb.gentoo.org/proj/sunrise.git/
1. Upstream is reasonably active, the latest release (2.1.2) came out in July 2018; 2. Licensing conditions have got me a bit confused - https://pyrxp.readthedocs.io/en/latest/introduction.html#license-terms says on the one hand that PyRXP has been released under the GPL (which makes sense given it links against RXP, which is distributed under the GPL as well) but on the other that one must purchase a licence if one wants to use it for a commercial product. I reckon they mean commercial NON-COPYLEFT products but that's just a guess; 3. The ebuilds would need a major overhaul in order to qualify for being added to the tree; 4. Is there in fact still any interest in adding this to Gentoo? If not, we shall close this ticket as WONTFIX in 30 days.
Is me enough for "any interest" to keep it in tree?
