Yes. Splitting out the distros was what I did with Marpa::{XS,PP} and
Marpa::HTML. I don't want to do that again because Marpa::R2::HTML
versions are tied tightly with Marpa::R2, and that kind of one-to-one
version tie-in does not play well with the way CPAN and cpantesters
works. CPAN assumes that you keep modules backward and forward
compatible, and implements other approaches as exceptions or not at all.
I learned this the hard way.
I don't mean to disparage CPAN's approach. Perhaps the single biggest
reason that Marpa was written in Perl was CPAN. CPAN's approach works
well in most cases.
-- jeffrey