Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

RFC: auto install C (and other) deps on OS level 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • ad 1: Yes, they do. Once I setup a yaml file to keep the names of all
    non-perl dependencies for some application. It looked roughly like
    this:

        - pngcrush

        - jpegtran:
                debian:
                    - libjpeg-progs
                redhat:
                    - libjpeg
                cygwin:
                    - jpeg

        - netpbm:
                debian:
                    - "netpbm-progs (>= 10.26.54-5)"
                    - "netpbm (>= 2:10.26.54-7)"
                redhat:
                    - "netpbm >= 10.26.39"

    So if you're lucky, then the package is called everywhere the same.
    Sometimes it's everywhere called completely different. Sometimes in
    one distribution some software components consists of one and in
    another of multiple packages. Sometimes you have to specify versions
    (I just used here the .deb resp. .rpm version syntaxes).

    I did not have the need to differentiate between various distribution
    versions, but I guess that there will be the some edge case when one
    has to specify different package names or versions for debian/lenny
    vs. debian/etch.

    ad 6: Why not put it into META.yml? Perl dependencies are already
    there, why not OS dependencies?

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.