I figure I've got PAUSE down, sort of. I had Bit::Vector all set, uploaded that, checked it in, and saw that it was duly registered, the Readme extracted, and so forth. When I downloaded off /incoming to doublecheck, naturally enough I found that the one thing I did manually (putting files in the proper places) when assembling the distribution (when I could have done it automatically) frigged up a file location for our Mac install procedures. So I used PAUSE 'delete', and that worked out OK. Other than resolving to doublecheck a .tgz on my own machine with 'installme', before I upload, which I neglected to do for this one (of course), I have another question - PAUSE evidently doesn't delete stuff for 48 hours or so. So I have to assume that until Wednesday evening I can't upload a fix? Correct? But after that it's OK? Any wisdom and knowledge on this much appreciated. Arved P.S. I'm going to have to checklist this whole procedure, and automate it some more. Between sticking original files where you want the ported ones to go, and vice versa, and things of that nature, I'm finding a number of things here that can derail a port or binary even though the 'blib' itself is OK. (In this case everything else was Ok - I screwed up the 'blib' tree. The original _did_ come from BuildProgram, but in the process of testing.... Don't ask. :-)) I'm thinking of a 'make dist' equivalent, basically. Some of this distribution editing is getting pretty old. :-) Any tips or comments? Paul and Chris, you guys have done this a lot - you use a checklist, or have some scripts in play? Just curious. ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org