I think that many of the problems shared by those components could be relieved by putting some teeth into Config.pm. Presently in P5, Config.pm has lots of potentially useful details about the local system, but many have the disclaimer in pod that they shouldn't be relied on.

System utility paths are reset to some vanilla value after configuration (bash, bison, byacc, cat, . . .). Why not leave them intact? Why not have a localization script which can correct those entries?

Config.pm seems quite accurate to me, but I'm on linux and I always build my own perl from source. That makes most things Just Work for me. With the fresh start of P6, there is the opportunity to tell vendors that the configuration must be accurate as installed and used on the local system.

After Compline,
Zaxo

In reply to Re: Perl6 - Distribution builder/installer by Zaxo
in thread Perl6 - Distribution builder/installer by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.