Yes, I emailed Donna a script which does basically this with the
/PERL/PUB/lib tree.  If anybody's interested, I can email it to them too.
It only stores/restores the changes and it makes a backup of files it is
going to overwrite.  It will also delete files on the production system if
they aren't on the development system, which a RESTORE won't do.

----- Original Message -----
From: "Mark Bixby" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, October 29, 2002 11:46 AM
Subject: Re: [HP3000-L] perl modules


> Development system:
>
> :STORE @[log in to unmask];*file;...
>
> Production system:
>
> :RESTORE *file;@[log in to unmask];...
>
> I do not know enough about Perl modules to know what you have to do to
move
> only a single module's files between Perl installations...
>
> - Mark B.
>
> Donna Garverick wrote:
> > in my environment, i've got a development system and a
> > production system.  the development system has all manner of
> > compilers and other development tools.  the production
> > system, otoh, doesn't.
> >
> > so trying to get perl modules onto the production system
> > leaves me in a bit of pickle -- mostly because the gnu (g++)
> > enviroment is (deliberately) not there.  is there a way to
> > move all the bits and pieces of a given perl module (and i
> > should probably add -- the *compiled* pieces) from one
> > system to another safely?           - d
> --
> [log in to unmask]
> Remainder of .sig suppressed to conserve expensive California electrons...
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *