home.social

#cpanm — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cpanm, aggregated by home.social.

  1. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  2. Grargh! hates extensions. And can't be configured to specifically use instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

  3. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  4. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  5. Grargh! #Solaris #tar hates #GNU extensions. And #cpanm can't be configured to specifically use #gtar instead of whatever tar it finds first in the path.

    Therefore ...

    `sudo ln -sf $(which gtar) $(which tar)`

    No, I'm not kidding.

    github.com/DrHyde/perl-modules

    #perl #ComputerAbuse

  6. @ferki @verzulli If I understand your requirements correctly, you could install a #perl version with #perlbrew on your local machine, install your required modules with #cpanm and provided libraries match between your dev and prod machines you can just copy the perl directory and run the perl with full path in the new location.
    If there is a library mismatch you are in a bit of pain to get it to work no matter what you do.
    May I suggest you build the restapi with #mojolicious?

  7. @ferki @verzulli If I understand your requirements correctly, you could install a #perl version with #perlbrew on your local machine, install your required modules with #cpanm and provided libraries match between your dev and prod machines you can just copy the perl directory and run the perl with full path in the new location.
    If there is a library mismatch you are in a bit of pain to get it to work no matter what you do.
    May I suggest you build the restapi with #mojolicious?

  8. @ferki @verzulli If I understand your requirements correctly, you could install a #perl version with #perlbrew on your local machine, install your required modules with #cpanm and provided libraries match between your dev and prod machines you can just copy the perl directory and run the perl with full path in the new location.
    If there is a library mismatch you are in a bit of pain to get it to work no matter what you do.
    May I suggest you build the restapi with #mojolicious?

  9. @ferki @verzulli If I understand your requirements correctly, you could install a #perl version with #perlbrew on your local machine, install your required modules with #cpanm and provided libraries match between your dev and prod machines you can just copy the perl directory and run the perl with full path in the new location.
    If there is a library mismatch you are in a bit of pain to get it to work no matter what you do.
    May I suggest you build the restapi with #mojolicious?

  10. I’ve just published a new Ansible module called perlmod_install_info whose purpose is to help you install Perl modules on systems in the most portable way possible.

    Specifically, this module knows how to search for Perl modules in dnf, yum, and apt repositories as well as in cpanm. It prefers the OS repositories over CPAN because generally speaking you’re better off going with the OS-packaged versions of modules when they’re available, both because that’s more robust and because the OS packages install much faster than CPAN. CPAN is needed as a backstop because the OS distributions don’t include all Perl modules.

    What’s especially clever about this module is that when it does need to resort to CPAN to find a module that isn’t available in the OS repository, it recursively determines all of the dependencies of that module and checks for them in the OS repository. It then returns lists of modules you can install from the OS and modules you need to install from CPAN, so you can minimize the number of modules that end up coming from CPAN.

    If this sounds useful to you, you can check it out on GitHub.

    #Ansible #apt #CPAN #cpanm #dnf #Perl #perlmodInstallInfo #yum

    https://blog.kamens.us/2023/09/13/just-published-perlmod_install_info-ansible-module/

  11. I’ve just published a new Ansible module called perlmod_install_info whose purpose is to help you install Perl modules on systems in the most portable way possible.

    Specifically, this module knows how to search for Perl modules in dnf, yum, and apt repositories as well as in cpanm. It prefers the OS repositories over CPAN because generally speaking you’re better off going with the OS-packaged versions of modules when they’re available, both because that’s more robust and because the OS packages install much faster than CPAN. CPAN is needed as a backstop because the OS distributions don’t include all Perl modules.

    What’s especially clever about this module is that when it does need to resort to CPAN to find a module that isn’t available in the OS repository, it recursively determines all of the dependencies of that module and checks for them in the OS repository. It then returns lists of modules you can install from the OS and modules you need to install from CPAN, so you can minimize the number of modules that end up coming from CPAN.

    If this sounds useful to you, you can check it out on GitHub.

    #Ansible #apt #CPAN #cpanm #dnf #Perl #perlmodInstallInfo #yum

    https://blog.kamens.us/2023/09/13/just-published-perlmod_install_info-ansible-module/

  12. I’ve just published a new Ansible module called perlmod_install_info whose purpose is to help you install Perl modules on systems in the most portable way possible.

    Specifically, this module knows how to search for Perl modules in dnf, yum, and apt repositories as well as in cpanm. It prefers the OS repositories over CPAN because generally speaking you’re better off going with the OS-packaged versions of modules when they’re available, both because that’s more robust and because the OS packages install much faster than CPAN. CPAN is needed as a backstop because the OS distributions don’t include all Perl modules.

    What’s especially clever about this module is that when it does need to resort to CPAN to find a module that isn’t available in the OS repository, it recursively determines all of the dependencies of that module and checks for them in the OS repository. It then returns lists of modules you can install from the OS and modules you need to install from CPAN, so you can minimize the number of modules that end up coming from CPAN.

    If this sounds useful to you, you can check it out on GitHub.

    #Ansible #apt #CPAN #cpanm #dnf #Perl #perlmodInstallInfo #yum

    https://blog.kamens.us/2023/09/13/just-published-perlmod_install_info-ansible-module/

  13. I’ve just published a new Ansible module called perlmod_install_info whose purpose is to help you install Perl modules on systems in the most portable way possible.

    Specifically, this module knows how to search for Perl modules in dnf, yum, and apt repositories as well as in cpanm. It prefers the OS repositories over CPAN because generally speaking you’re better off going with the OS-packaged versions of modules when they’re available, both because that’s more robust and because the OS packages install much faster than CPAN. CPAN is needed as a backstop because the OS distributions don’t include all Perl modules.

    What’s especially clever about this module is that when it does need to resort to CPAN to find a module that isn’t available in the OS repository, it recursively determines all of the dependencies of that module and checks for them in the OS repository. It then returns lists of modules you can install from the OS and modules you need to install from CPAN, so you can minimize the number of modules that end up coming from CPAN.

    If this sounds useful to you, you can check it out on GitHub.

    #Ansible #apt #CPAN #cpanm #dnf #Perl #perlmodInstallInfo #yum

    https://blog.kamens.us/2023/09/13/just-published-perlmod_install_info-ansible-module/

  14. I’ve just published a new Ansible module called perlmod_install_info whose purpose is to help you install Perl modules on systems in the most portable way possible.

    Specifically, this module knows how to search for Perl modules in dnf, yum, and apt repositories as well as in cpanm. It prefers the OS repositories over CPAN because generally speaking you’re better off going with the OS-packaged versions of modules when they’re available, both because that’s more robust and because the OS packages install much faster than CPAN. CPAN is needed as a backstop because the OS distributions don’t include all Perl modules.

    What’s especially clever about this module is that when it does need to resort to CPAN to find a module that isn’t available in the OS repository, it recursively determines all of the dependencies of that module and checks for them in the OS repository. It then returns lists of modules you can install from the OS and modules you need to install from CPAN, so you can minimize the number of modules that end up coming from CPAN.

    If this sounds useful to you, you can check it out on GitHub.

    #Ansible #apt #CPAN #cpanm #dnf #Perl #perlmodInstallInfo #yum

    https://blog.kamens.us/2023/09/13/just-published-perlmod_install_info-ansible-module/

  15. I tried to tinker a bit with some Git branch for a future #PullRequest before “doing the real work” …

    Now I’ve dug deeply into `cpanm` code, created two truth tables of 32 cases each and lost the whole day writing a lengthy update on this #GitHub issue. 😂
    github.com/miyagawa/cpanminus/

    The issue is actually about building small #Docker containers with minimal @Perl dependencies while using the #CPAN client #cpanm alias #cpanminus.

  16. I tried to tinker a bit with some Git branch for a future #PullRequest before “doing the real work” …

    Now I’ve dug deeply into `cpanm` code, created two truth tables of 32 cases each and lost the whole day writing a lengthy update on this #GitHub issue. 😂
    github.com/miyagawa/cpanminus/

    The issue is actually about building small #Docker containers with minimal @Perl dependencies while using the #CPAN client #cpanm alias #cpanminus.

  17. I tried to tinker a bit with some Git branch for a future #PullRequest before “doing the real work” …

    Now I’ve dug deeply into `cpanm` code, created two truth tables of 32 cases each and lost the whole day writing a lengthy update on this #GitHub issue. 😂
    github.com/miyagawa/cpanminus/

    The issue is actually about building small #Docker containers with minimal @Perl dependencies while using the #CPAN client #cpanm alias #cpanminus.

  18. I tried to tinker a bit with some Git branch for a future #PullRequest before “doing the real work” …

    Now I’ve dug deeply into `cpanm` code, created two truth tables of 32 cases each and lost the whole day writing a lengthy update on this #GitHub issue. 😂
    github.com/miyagawa/cpanminus/

    The issue is actually about building small #Docker containers with minimal @Perl dependencies while using the #CPAN client #cpanm alias #cpanminus.

  19. I tried to tinker a bit with some Git branch for a future #PullRequest before “doing the real work” …

    Now I’ve dug deeply into `cpanm` code, created two truth tables of 32 cases each and lost the whole day writing a lengthy update on this #GitHub issue. 😂
    github.com/miyagawa/cpanminus/

    The issue is actually about building small #Docker containers with minimal @Perl dependencies while using the #CPAN client #cpanm alias #cpanminus.

  20. Having always used with I'm now looking into and find it an interesting concept. However, with cpanm and a I can declare a feature which include dependencies that are only installed when I pass the flag to cpanm. But it seems this isn't possible to do with Carmel?

    @Perl

  21. Having always used #cpanm with #perl I'm now looking into #Carmel and find it an interesting concept. However, with cpanm and a #cpanfile I can declare a feature which include dependencies that are only installed when I pass the flag to cpanm. But it seems this isn't possible to do with Carmel?

    @Perl

  22. Having always used #cpanm with #perl I'm now looking into #Carmel and find it an interesting concept. However, with cpanm and a #cpanfile I can declare a feature which include dependencies that are only installed when I pass the flag to cpanm. But it seems this isn't possible to do with Carmel?

    @Perl

  23. Having always used #cpanm with #perl I'm now looking into #Carmel and find it an interesting concept. However, with cpanm and a #cpanfile I can declare a feature which include dependencies that are only installed when I pass the flag to cpanm. But it seems this isn't possible to do with Carmel?

    @Perl

  24. Having always used #cpanm with #perl I'm now looking into #Carmel and find it an interesting concept. However, with cpanm and a #cpanfile I can declare a feature which include dependencies that are only installed when I pass the flag to cpanm. But it seems this isn't possible to do with Carmel?

    @Perl