I'd like to try out this XML formatter. From the Homepage: "xmlroff is a fast, free, high-quality, multi-platform XSL formatter that aims to excel at DocBook formatting and that integrates easily with other programs and with scripting languages." xmlroff depends on pangoxsl; I will supply the ebuild for that as well. The License looks open enough to me, but I could not find an identical one in the licenses directory, so this probably has to be a new license file. I'm not sure if deleting the html documentation is the right thing to do if doc is not specified. It is installed by default. On the other hand, it is over 8 MiB, people not installing docs probably want to save that space. There is also a package named libfo-jni that could provide java bindings to xmlroff. I thought about including this in the ebuild, but I believe it is better of in a standalone ebuild. I will not write this at the moment, because I don't have the time right now and because a java package freeze is in effect.
Created attachment 80874 [details] app-text/xmlroff/xmlroff-0.3.9.ebuild
Created attachment 80875 [details] x11-libs/pangoxsl/pangoxsl-1.6.0.2.ebuild
I found out that the license for xmlroff is specified as "BSD" on the sf project page. The formatting is different, and there is an additional paragraph about nuclear facilities, which seems to be part of most Sun licenses, but is not part of the original BSD license.
Created attachment 143306 [details] app-text/xmlroff/xmlroff-0.5.4.ebuild version bump. it does not require the pangoxsl anymore, it is now part of xmlroff.
Created attachment 149043 [details] app-text/xmlroff/xmlroff-0.5.5.ebuild There is a new version. xmlroff now has a domain of its own, and no longer uses the sf distribution system. The attached ebuild reflects this.
Created attachment 173439 [details] There is a new version app-text/.xmlroff-0.6.1
Created attachment 173441 [details] File name fixed. Sorry for my confusion and flood just ignore other ebuild file. Regards, Behzat.
(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. Heuristics show that no Gentoo developer has commented on your ebuild. 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
Comitted to sunrise, should appear soon at the following location: http://overlays.gentoo.org/proj/sunrise/browser/reviewed/app-text/xmlroff/
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/