comment on

So I build and I test, trying to try out an sdl example and poop, can't load libsdl yada yada.

So I run Configure.pl with the --ask option (making sure all my libs are in a row), and I figure what the hey, I might as well install this time (nmake install), and what do I see? I see perl.exe yada yada yada | sh error error.

Confused? Me too. You need perl to configure, a make program to make, but what do you need sh for?

I guess that's the price of progress, someone on the development team don't know much about perl (or don't got time to reinvent install.sh or whatever) and that's what you end up with.

I wonder when that happened :(

Hmm, install (looks like the right one) is nicely spaced plenty of comments, and still only 250 lines. Opportunity? I think so. Who knows sed/awk? :)

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

In reply to the price of progress by PodMaster
in thread Leaping Kakapo by liz

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks