"Ralf S. Engelschall" <[EMAIL PROTECTED]> writes: > Currently there is no way to automatically create .spec files to > package CPAN modules, although all of our perl-xxx.spec files we have > in OpenPKG-CURRENT look very similar (they all have the same prolog and > epilogs. So you can just take a simple one like perl-term.spec and use > it as a template. > > The modules included in our current "perl" package are already under > consideration to be moved to their own "perl-xx" packages. So you can > be sure that we do not remove a module at all, but it is likely that > they move from "perl" to "perl-xx" to be consistent with the other > modules. My current idea is to create a "perl-std" package where all > those standard and self-contained modules are collected.
Hmmm, that seems reasonable. Thanks. I've just noticed the "cpanflute" utility that comes with rpm, but it looks like the output spec file would need quite a bit of work. Thanks, -Dom -- | Semantico: creators of major online resources | | URL: http://www.semantico.com/ | | Tel: +44 (1273) 722222 | | Address: 33 Bond St., Brighton, Sussex, BN1 1RD, UK. | ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
