Using EPIC to develop code only

gservat wrote on Wed Oct 18 22:26:00 MEST 2006:

Hi,

I'm using EPIC to write code and once I've done that, I need to upload it
to a server where the required Perl modules, etc, are installed (and ultimately
where the scripts will run).

I looked into CVS. CVS is not quite the right solution as it involves checking
out from EPIC which is all well and good, but then I need to go into the
remote server and do a cvs checkout. That's not the bad part. The part I
don't like is that all my "use .." lines in the Perl modules come up with
a big bad red cross. Is there any way to make EPIC ignore the "use" lines?
if not, how do people do it?

Apart from the CVS solution, I also looked into the FTP synchronization
solution which looked OK at first, but when I did a compare between remote
and local, remote always came up totally blank for some reason that I couldn't
figure out. It also has the same problem that the "use .." lines have an
error associated to them since the modules aren't installed locally, they
are installed remotely.

Thanks very much in advance for any tips, suggestions, whatever comes my
way.

Regards,
Gonzalo.

jgangemi wrote on Wed Oct 18 22:48:27 MEST 2006:

you could turn off validation, but i don't see that being the most ideal
solution.

can you mount the remote module directory on your local machine and set
an include path for it? 

i'm in a similiar situation w/ my dev work, but i just install any 3rd party
modules that might be required on my local dev machine.

gservat wrote on Wed Oct 18 23:40:42 MEST 2006:

Hi, thanks for your reply.

That's how I've been doing it. Mounting the remote directory on my local
PC which works great when I'm near the dev machine, but when I work from
home I press save on Eclipse and it might take 5 mins, sometimes it doesn't
finish and I have to kill the app.

What you're suggesting is to mount just the modules directory remotely which
is a work around I guess. Not the ideal solution but I guess it does the
trick.

Have you ever used the FTP sync option? That would solve my "saving" problem,
although it doesn't work for me very well (as I said in my post). The remote
side is always blank. It would seem like it can't download the file or something
but if I tell Eclipse to download it, it can do it no probs. It's just comparing
that doesn't work.

Regards
Gonzalo

jgangemi wrote on Wed Oct 18 23:55:53 MEST 2006:

any reason you can't install the libraries that are missing on your local
dev machine?

gservat wrote on Thu Oct 19 00:00:53 MEST 2006:

Mainly because the scripts always run on a Linux box, and I'm developing
on a Windows box (unfortunately, it's a work restriction imposed on me).
Some of the modules I need have dependencies all over the place, so I don't
know how easily or hard it'd be to get them installed. If it was a Linux
box, I would have installed them by now and used CVS or something to connect
remotely to the Linux box. Infact, it would even serve the purpose to test
them locally before comitting. The type of development I'm doing is code
code, submit, test, code code, submit, test, etc.. so it's not really suited
for CVS as the idea behind CVS, as far as my understanding goes, is to modify
code then commit once you're happy with the changes, NOT make lots of little
commits.

jploski wrote on Thu Oct 19 20:33:10 MEST 2006:

Like Jae, I think that installing the needed modules under Windows would
be worthwhile. The PPM package manager from ActiveState is almost as good
as the CPAN shell in my experience. If we are talking about custom modules
here, you should be able to make them deployable via CVS yourself, and install
their dependencies using PPM. Getting the local include path right takes
some effort because EPIC tends to misreport the 'compilation failed in require'
errors (so it is a good idea to rely on perl -c when setting up your environment).

If you *really* don't want to install the needed modules, you could perhaps
use a trick to get rid of the error messages: create a bunch of fake modules
which contain nothing (just the correct package name) and put them on the
include path in project properties.

CVS commits are supposed to be coherent because otherwise you can hardly
write meaningful commit comments. Another reason is to keep developers working
on the same branch from stepping on each others' toes, but it does not seem
to be an issue for you.

jgangemi wrote on Thu Oct 19 20:47:25 MEST 2006:

i also had success using cygwin's perl under windows as well. i believe
the only module i really had an issue with was for mysql. 

i had to download mysql 4.x and compile it from scratch in order to get
DBI::Mysql to build correctly, but otherwise, no issues.

gservat wrote on Fri Oct 20 03:51:44 MEST 2006:

Thanks for all the replies. I think I just need to find a PPM source for
CPAN modules so that I can install them. All the modules I'm using in my
scripts come from CPAN (such as Net::SSH::Perl) so once I manage to find
a PPM CPAN source, I should be able to install them and be good to go.

Thanks again!