Surely $Config{installsitebin} should be in the path - even if no such directory exists initially.

I'd never even heard of $Config{installsitebin} prior to this discussion. I've no idea where it comes from or who invented it. From a quick google, it appears to be modelled after /usr/sbin, and therefore completely alien to Windows.

I've no idea how I (as an (AS)Perl user) would ever think to add a random directory, that isn't mention anywhere, to my path; especially if it doesn't exist (yet).

As a programmer, I would steadfastly NOT add a non-existent directory to my path. And as a matter of course, I routinely trim my path to containing just those directories that contain things I use.

All I'm doing is having PPM overwrite an existing file (installed by a previous 'ppm install') with an *identical* file.

I agree that needing --force to overwrite identical files is stupid.

But I also think that given that you are incorporating a version into your renamed DLLs, there is no need to use installsitedir. Nor to make the names unrecognisable either.

If you renamed your package-attached version of libgcc_s_dw2_1.dll to libgcc_s_dw2_1.nnn.dll, I think that they could all (libgcc_s_dw2_1.dll; libgcc_s_dw2_1.463.dll; libgcc_s_dw2_1.471.dll etc.) be put into perl\bin and coexist there without conflict, and without needing the extra directory or further additions to the path.

But, having failed to make the SxS thing work -- though I'm pretty certain I did when I first investigated the issue 3 or 4 years -- I'm not suggesting you pursue this any further. In fact, I strongly recommend against it on the basis that I have no desire to send you down any further dead ends.

But still the nagging doubt that what you have now, is repeating the mistakes of the past, persists. But I can live with that.

So, once again, sorry for the misdirection; I hope that overall I helped more than hindered.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

RIP Neil Armstrong

In reply to Re^8: Module::Install hacking by BrowserUk
in thread Module::Install hacking by syphilis

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.