Of course the files that get installed end up in the blib first. That's how things like `make test` get a chance to do things before you install anything, and it's how the installation process figures out what it needs to install where. Furthermore, files that other programs create (i.e. PL_FILES, MAN\dPOD, and so on) show up in their final form in blib before they get installed. The user can watch the build process and see any errors without polluting their system and then tracking down all of the files.

Because a couple of Makefile.PLs are complex, you want to change everything? A lot of Makefile.PL files aren't complex.

But now we start to see your real gripe: the current system adds an extra CC flag that generates warnings for you. Other people have had the extra flag problem, and the Perl community has community has fixed it.

I think your gripe is that you just don't know enough about how it works to play with it. Sure it's hard at first, but why let that scare you?

--
brian d foy <brian@stonehenge.com>

In reply to Re^5: CP6AN should be a database by brian_d_foy
in thread Notion: CP6AN <strike>should</strike> could be a database by BrowserUk

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.