Thanks, the symlink approach seems to fit what I'm after. There are subclasses in my module (Foo::Bar::Baz) so I guess I'll try linking the directory rather than just one file.
What I'm trying to do seems like it should be easy: make a module skeleton with h2xs, work on it in place, and finally make a release from it. The "work on it in place" is turning out to be surprisingly difficult. So far I've just installed it into a local directory (so that I don't have to edit it as root) and I'll have to copy it back into my release directory structure when I have a version that's ready to go. I can live with that, but I expected to be able to work on it directly in place after creating it with h2xs.
I'm using the module in the context of mod_perl, so being able to run it from scripts outside of the module's directory is necessary.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
