PortageXS is probably a great idea, but there is no way for me to know. 1. It took me a while to work out who the author was, the "website" for it is just a http/ftp directory, and that is very unhelpful. 2. Author is a Gentoo Dev. # author : Christian Hartmann <ian@gentoo.org> 3. There is no upstream location to file bugs, and there is no upstream location stated in metadata.xml, though Gentoo bugzilla can probably process bugs for it, its not intuitive. 4. Documentation is sparse / missing. No man pages, no perldoc . I could read the source, or read the several dozen examples, but examples and source are no replacement for documentation. 5. It is not even clear if this distribution is usable on not-strictly-gentoo systems ( even if set up right ), for instance, if this distribution can parse ebuilds in a programmingly useable manner, then it would be useful to people of other distributions, and thus, would be good to have on CPAN. 6. Its impossible for me to write a Perl module that depends on this and then release it to CPAN. Thanks.
@Kent, maybe you want became upstream for this module? How i know you have access to the perl-experimental overlay too. Personally i have *really* too many work with portage tree, that should be done. And i have no time for maintain this package as upstream developer. Ian retire for now, and i don't know how contact him.
I'll have a more serious look at it this afternoon, I'm good with Dist::Zilla and friends, just not so familiar with the XS Bits of things, but assuming I can get somebody else to deal with XS problems, I can be release manager.
(In reply to Kent Fredric from comment #2) > I'll have a more serious look at it this afternoon, I'm good with > Dist::Zilla and friends, just not so familiar with the XS Bits of things, > but assuming I can get somebody else to deal with XS problems, I can be > release manager. Let me know when you ready. By the way, may be you want maintain it in the main tree via proxy-maint project?
I'm now sort of confused after looking further, I had the impression this was an XS library, hence, PortageXS, however, theres' nothing XS-like at all in here. Nothing. The XS Suffix is thus just confusing. And CPAN are somewhat averse to people populating the top namespace, just not sure if we can really change this at this point. At this stage I'm inclined to want to rename it Gentoo::Portage::API or something like that. Its not too hard to do that source side, but its going to be a little messy asking the dependents in portage to adapt.
Ok, I think I can get it going as-is. We can fix the naming up later anyway, its just temporary ugliness. Going to cut a 0.2.12 release with a few minor fixups, predominantly merging the paths patch ( with additional stuff to fallback ). Eventually going to try reduce the amount of patching required to make it work on PREFIX, because blegh. I've looked into the code enough to know that I can overhaul lots of it and make it better, lots of stuff it does is pretty ugly and needs to go. Though, I have really no idea how to go about getting myself on the proxy-maint wheel here, this part of Gentoo seems to regularly phase me. ( Been meaning to do the dev questions for 2 years now, always simply never manage to complete them )
https://metacpan.org/release/KENTNL/PortageXS-0.2.11 Will get started on updating the ebuild now.
Ok, i close this bug now. I think we get version bump a little later :)
