Koen made a similar comment via private email. I am happy to follow the Debian convention. I will resubmit the entire series.
Thank you for the input. Regards, Tim On Fri, Jan 31, 2014 at 9:26 AM, Olof Johansson <[email protected]>wrote: > On 14-01-31 16:11 +0100, Tim Orling wrote: > > This module provides a standard way to gather metadata about a > > .pm file through (mostly) static analysis and (some) code > > execution. When determining the version of a module, the > > $VERSION assignment is "eval"ed, as is traditional in the CPAN > > toolchain. > > For me, it seems strange to skip out the first part of the module > name, just because it's part of the recipe perl-module- prefix. I > agree it's a bit ugly to call it perl-module-module-metadata, but > I think it would cause less confusion. > > On the other hand, the naming convention within meta-perl seems > to be consistently lib<module name>-perl, like it is in Debian. > Same for oecore, except the core modules provided by the perl > recipe. This would make the proper name for this recipe be > libmodule-metadata-perl. Why use the perl-module- prefix? > > Regards, > -- > olofjn > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
