comment on

And now I have to move to a new platform to test it all again. The setup script should be close to what I need, but, of course the stuff I typed at the command line needs to be rewritten on the new machine...

Are you asking about building your build scripts? I don't see why build scripts can't be treated as another package. The Unix way to handle cross-platform builds is configure (the docs even say there is Win32 support). The Perlish way is Module::Build or MakeMaker.

If you don't want to carry Perl around, it sounds like you may just want a variant of make clean that only impacts the 'build scripts', whatever they are. Makefiles are not Perl specific, all the platforms you mention should have a version of make (nmake for windows).

Or, maybe I've missed your point entirely.

--Solo

--
You said you wanted to be around when I made a mistake; well, this could be it, sweetheart.

In reply to Re: proving something other than perl by Solo
in thread proving something other than perl by Tanktalus

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.


There's more than one way to do things
	PerlMonks