in reply to Re: Appending $VERSION to package name in Makefile.PL
in thread Appending $VERSION to package name in Makefile.PL

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 :-)

Replies are listed 'Best First'.
Re^3: Appending $VERSION to package name in Makefile.PL
by tobyink (Canon) on Apr 19, 2012 at 10:22 UTC

    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.

    Use a layout like this:

    bin/myscript.pl
bin-testing/myscript.pl
lib/My/Module.pm
lib-testing/My/Module.pm

    [download]

    Then, to run the stable service:

    perl -Ilib bin/myscript.pl --port=1234

    [download]

    And for the testing service:

    perl -Ilib-testing bin-testing/myscript.pl --port=1235

    [download]
    perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'
[reply]
[d/l]
[select]
Re^3: Appending $VERSION to package name in Makefile.PL
by Anonymous Monk on Apr 19, 2012 at 08:06 UTC
[reply]
[reply]

      Thanks.

      The target layout is pretty clear by now, and I even know what I'd have to do when doing it "by hand".

      What I'm trying to do now is to coax MakeMaker into doing it for me (bonus points if it does a "stage install" by default, so as not to thrash the "hot" installation).

      Regards
[reply]
[reply]

In Section Seekers of Perl Wisdom