Some clarifications: There is for example a lot of logic in the package DhMakePerl::Command::Packaging that I'd like to reuse for java packaging. For that I'd need a reliable API and some logic would need to extracted from larger functions into separate functions:
* get_developer(), get_wnpp() are fine for reuse * fill_maintainer() has hardcoded reference to perl team * set_package_name() contains logic to fall back to create a perl library package name * extract_desc() contains useful logic to format the long package description * ... I think it's fine to keep all this logic in the dh-make-perl package. It would just be helpful to have a clear distinction between reusable code that could be used for languages other than perl and code specific for packaging perl. I'm just starting to learn perl, so it'll take some time until I can help with this. Regards, Thomas Koch, http://www.koch.ro -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
