use Perl

• Thanks (Score:1)

  by berekuk (9275)

  Thanks for this, I would love to hear more similar stories from other people.

  In our case, we are still trying to be perfectionists and maintain >300 in-house .deb packages and several hundreds of hand-builded cpan packages as well.
  Actually, in our case our "application" consists of many various scripts and daemons, working on different hosts and clusters, so it is impossible to pack everything in one package anyway.

  I've been dreaming for a long time about fully-automated cpan-to-deb (and cpan-to-rpm) bui
  • Re:Thanks (Score:1)

    by brother (3287) on 2010.07.20 7:25 (#72189) Homepage

    <p>I have just given up handling dependencies with one debian package per cpan distribution. For some time I have thought about how to build a bundle in the most maintainable way.
    
    <p>My current solution is to build a quite clean chroot of Debian Lenny and then use cpanm to install some modules in /usr/local and as the last step I'm making a package with everything in /usr/local. The chroot is build with:
    
    # debootstrap --arch amd64 --variant=buildd --include=cdbs,libwww-perl lenny /mnt http://ftp.se.debian.org/debian/
    
    And then I have a simple Makefile installing everything needed:
    
    #!/usr/bin/make
    
    build:
                    PERL_MM_USE_DEFAULT=1 perl -MCPAN -e 'CPAN::Shell->install("App::cpanminus")'
                    cpanm Moose AnyEvent JSON:XS Yadda:Yadda:Yadda
    
    install:
                    install -d $(DESTDIR)/usr/local
                    cp -a /usr/local/* $(DESTDIR)/usr/local
    
    For the cpan-to-deb buildfarm, have you looked at Jos Boumans' work with http://debian.pkgs.cpan.org/ (No, I don't considder CPANPLUS::Dist::Deb as good as the packages generated by dh_make-perl and the Debian Perl Group - but it might be a good place to start)

    Reply to This

    Parent