Pelican is available on GitHub, and I noticed there wasn't a live ebuild for it. Attached is a patch for version 9999. I'd add it myself but I chose to follow protocol. Reproducible: Always
Created attachment 435514 [details, diff] pelican-9999.patch Patch to provide pelican live ebuild. Tested it on my machine and it works. Let me know if I'm missing anything.
Any particular reason for adding one?
The same reasons for anyone to add or use a live ebuild; if you're collaborating with upstream or are helping to test it, or developing things that make use of the latest features, etc. I understand that this particular upstream tends to change things in subtle ways, so if you don't think it's worth the burden of maintenance just let me know and I'll put it in my overlay.
Okay, feel free to put it in. Want to be co-maintainer? :)
Sure, I can handle that. I run Gentoo on a VM and the latest Pelican, so I'd definitely notice bugs when they come up. Should I clarify that I maintain just the live ebuild, or do you want to share maintenance for the whole package?
Would you mind co-maintaining the whole thing? I'm not particularly territorial; the main reason I maintain pelican is that I use it myself, so I like to make sure reasonably recent versions of it hit the tree (I also contributed something upstream once IIRC).
(In reply to Dirkjan Ochtman from comment #6) > Would you mind co-maintaining the whole thing? I'm not particularly > territorial; the main reason I maintain pelican is that I use it myself, so > I like to make sure reasonably recent versions of it hit the tree (I also > contributed something upstream once IIRC). Sure, not a problem. :) I'll go ahead and add myself to metadata.xml, then commit the live ebuild if it looks good to you.
Resolved by commit 125534a046099a8f5ef374c552f17897cf87c2fe: app-text/pelican: Add live ebuild
