new-cpan.sh, pldcpan and pure_install

Elan Ruusamäe glen at delfi.ee
Sun Nov 6 21:29:08 CET 2005


On Sunday 06 November 2005 21:20, Bartek Jakubski wrote:
> Large part of new-cpan.sh script is unnecessary - pldcpan handles tar.gz
> archives just fine (and inserts md5 sums too). Using pure_install
> instead of install is trivial to change in pldcpan (spec template is at
> the end of pldcpan file).
new-cpan.sh was created because pldcpan inability to fetch sources remotely. 
rest of that just evolved so. improving pldcpan to have that functionality is 
great idea, just do it :)

> The remaining functionality seems to be accepting module name or URL on
> command line (instead of just filename) and cpan2rpm is used for that.
> But is this functionality so important to leave new-cpan.sh in SPECS?
> (not to mention that I will probably implement something like that in
> pldcpan).
>
> I also have some other pending changes to pldcpan - radek: can
> I commit freely or you want to review them before?
>
> Talking about pure_install - if really we should use it then I guess
> that there should be a mass commmit made among perl-* specs?
afaik it's not so simple, some packages implement local hooks to install data, 
so imho each package must be reviewed separately. but in most cases the only 
difference is creating perlocal.pod

-- 
glen



More information about the pld-devel-en mailing list