I have a machine on which I'd like to run spamassassin. But it's behind an air gap. It's not on the internet. I've been downloading missing perl packages a handful at a time, but I despair of the list ever coming to an end.
1. I _might_ (and might not) be able to put a similar machine outside the air gap. If I install spamassassin on it, is there any way to log what extra packages spamassassin brings in to satisfy dependencies? If I knew what was brought in, I could get all the dependencies at once. 2. Or does somebody have this list of dependencies already? 3. Or, should I do item (1) above and then tar up the perl tree? Is it going to go to a different perl tree? FWIW the box is (or will be) running linux. (I'm ready to give up on this, frankly.) j. -- Jay Scott 512-835-3553 g...@arlut.utexas.edu Head of Sun Support, Sr. System Administrator Applied Research Labs, Computer Science Div. S224 University of Texas at Austin
