I have created an ebuild: https://github.com/basiliscos/nanga/blob/master/dev-perl/Path-FindDev/Path-FindDev-0.4.1.ebuild Please, review it. Reproducible: Always
https://github.com/basiliscos/nanga/blob/master/dev-perl/Path-FindDev/Path-FindDev-0.4.1.ebuild
I'm upstream for this, so if you could add me as something proxy-mainty in the metadata that'd be helpful. Observations/Questions: Ebuild depends on Class::Tiny 0.11.0 when the package only depends on 0.10.0 itself, whats the reason for the discrepancy? Path::IsDev v0.2.2 is a minimum requirement, but the ebuild states >=1.0.0, this is acceptable, just again, discrepancy from the code upstream adds scope for later confusion. Path::Tiny dependency says >=0.44.0 , when upstream only says >=0.38.0, again, I don't so much have the problem with the newer deps, just lots of people loathe "needless upgrades" if they can avoid it, deps that are too steep may needlessly hamper stabilization. Upstream has no stated dependency on a specific version of Sub::Exporter, so this just seems weird to say ">=dev-perl/Sub-Exporter-0.984.0". Other than that its looks fine to me. If the above dependencies have a real cause behind them that matters, I'd love to know about them so I can bake them in upstream, imo, gentoo deps and upstream deps should be as logically similar as practically possible.
(In reply to Kent Fredric from comment #2) > I'm upstream for this, so if you could add me as something proxy-mainty in > the metadata that'd be helpful. OK. How to do that? Like the following? <herd>proxy-maintainers</herd> <maintainer> <email>kentfredric@gmail.com</email> <name>Kent Fredric</name> <description>Proxied Maintainer</description> </maintainer> > Observations/Questions: > > Ebuild depends on Class::Tiny 0.11.0 when the package only depends on 0.10.0 > itself, whats the reason for the discrepancy? > > Path::IsDev v0.2.2 is a minimum requirement, but the ebuild states >=1.0.0, > this is acceptable, just again, discrepancy from the code upstream adds > scope for later confusion. > > Path::Tiny dependency says >=0.44.0 , when upstream only says >=0.38.0, > again, I don't so much have the problem with the newer deps, just lots of > people loathe "needless upgrades" if they can avoid it, deps that are too > steep may needlessly hamper stabilization. > > Upstream has no stated dependency on a specific version of Sub::Exporter, so > this just seems weird to say ">=dev-perl/Sub-Exporter-0.984.0". > > Other than that its looks fine to me. > > If the above dependencies have a real cause behind them that matters, I'd > love to know about them so I can bake them in upstream, imo, gentoo deps and > upstream deps should be as logically similar as practically possible. Thanks for detailed explanation. I just have fixed them. I didn't have any particular "dependency policy", so, I just picked up the most fresh dependency fron CPAN, made an ebuild for it, and then pin it. (A-la cpanm behaviour). I'll be more accurate in future.
Its probably applicable to <herd>perl</herd> too (ie: multiple herd tokens is acceptable ), but other than that, I think thats how we do it. There's not any huge reason usually why any one specific person should be maintainer on it in perl land, they're usually straight forward enough that anyone in perl herd ( or often, people outside it ) can handle bumping and soforth =) Just the right bits on metadata means more ( and more relevant ) people will be notified when bugs are filed, I think.
OK, thanks. I just have added the metadata: https://github.com/basiliscos/nanga/blob/master/dev-perl/Path-FindDev/metadata.xml
Is anyone still interested in this? If yes, please say so here and now!
Ugh. I know why this was filed, and the needed blocker wasn't added. Adding that now. This is in the class of "I wrote this, and I regret that fact" ;)
dev-perl/Path-FindDev now in tree.
