Thanks, Eliya for your insights.
In the long run, keeping all code in sync that references the module gets a little unwieldy for my taste

That's why I wanted Makefile.PL to do the dirty work for me.

Of course, I'd strive for it writing the right incantations into the script such that it finds "its" modules.

I'd rather use a version control system to quickly check out / switch between multiple versions — if that is the idea.

I slowly notice how sloppy I was in describing my problem.

The script is a network server, and I wanted the alternative ("staging") version to provide a new version of the service (perhaps on a different port) for the users to test, without disrupting the current (stable) service.

Or, if you prefer multiple physical subdirectories named after the versions, put another directory above the root of the module name space, i.e. .../0.9/My/Module/Submodule.pm

That's it! This schema makes much more sense.

Now how would I get MakeMaker to do that for me (e.g. saying 

  perl Makefile.PL STAGING=yes

[download]
would I have some ideas about point 3 above (I'd have to provide a script template, script.PL which would write out the script with some substitutions), but I'm somewhat lost on 1 and 2.

Sure, that doesn't allow things like My-1.1/Module-0.9/Submodule-2.3.pm, but I'm not sure if that's a good idea anyway :)
No, I'm not *that* crazy ;-)
P.S.: use My::Module-0.9 wouldn't work for syntactial reasons — you'd at least need something like My::Module0_9
You are absolutely right. The idea you've given to me above is far better, anyway. Thanks again, I'm a step closer now :-)

In reply to Re^2: Appending $VERSION to package name in Makefile.PL by oldtomas
in thread Appending $VERSION to package name in Makefile.PL by oldtomas

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.