Thomas Frohwein <tfrohwein@fastmail.com> wrote:
> *ping*
> 
> This can save enough work with ports that have multiple submodules that
> I think it might help porters' work. Of course this can be obtained
> from the GitHub source, too, but having it in the ports tree would help
> visibility and accountability, especially to decrease the barrier for
> working with complex ports. Re-attaching for convenience.

I've quickly tested it and it seems to work as advertised.  In my
experience there are not that many ports needing to use submodules (or
maybe i was just lucky ;-) but nevertheless it's nice to have something
in the port infrastructure to automatize that bit.  Seems also quite
simple too, which is promising.

With a few more lines of code to grok the .gitmodules ini file, we could
also be able to avoid using the github api, which would make make even
easier to extend it for other forges.

I don't have lots of experience with perl but it reads fine to me.  Oh,
Readonly.pm is not in base though :P

So, fwiw I'd welcome something like this in the port infrastructure.

crazy idea: what about hooking something like this into portgen and then
allow to do `portgen github johnfactotum/foliate'? :-)