# from David Golden
# on Wednesday 20 August 2008 15:10:
>> Of course, by trying to make it abstract and reusable, I'm just
>> making unnecessary work for myself because every author with more
>> than 3 modules writes their own kit? At least, that's the
>> impression I get whenever I mention it.
>
>Whipuptitude beats manipulexity for this class of problem, perhaps? I
>can hack up my own kit faster than I can learn and configure someone
>else's? And once written it's fairly stable.
True and true. Your code looks a lot like my config file though, except
for the git bit. So, you have a server named 'echo' too? Is there an
echo in here?
try "git archive --format=tar --remote=$repos $fulltag | tar -xf -";
try "$perl Build.PL";
try "$perl Build";
try "$perl Build testpod";
try "$perl Build distcheck";
try "$perl Build dist";
try "$perl Build disttest";
Well, I skipped the "Are you sure?" bit because of course I'm sure! It
helps that the code is tested. But there's a stop directive for that
purpose (I think when I left off I was pondering how to
have --stop-after-... or --fake options on the command line.)
process:
- clean
- create_build
- .test
- .testpod
- .testpodcoverage
- .dist
- check_manifest
- check_kwalitee
- check_changes
- .disttest
- check_version_control
shipit:
- tag_version_control
- scp_relay
- pause_http_relay
Oh, and I hate the part where I make a fake pause cgi to test it :-)
--Eric
--
"Matter will be damaged in direct proportion to its value."
--Murphy's Constant
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
