Perl scripts in /iw-bin

Hi All -

I wanted to pick the brains of the DevNet community on this one.

We have a Windows-based lab where our goal is to promote Perl code base to a target Solaris OS running Interwoven TeamSite (6.7.1 SP2)

We check the OS in our Perl scripts and change paths etc. accordingly, and this works fine. We also have a script that executes after the files are transferred to do any dos-2-unix work, permissions etc.

The last issue that we are trying to tackle is dealing with the shebang line for any scripts located in /iw-bin. I can't see a way of dealing with this dynamically in a Perl script, but I would be open to any insights someone might have on this.

We are considering doing processing on the file, but it becomes a pain in the but because we use CVS as our sc repository. We would have to process the file after checkout to make it work in Windows, then process it again before we check it back into CVS.

Is there a way to handle this in CVS?

Thanks in advance,
Lucas

Find more posts tagged with

Comments

vpatel

Do you have a custom build process that propogates your code from CVS to target TS environment?

Ottawa_IWOV

Do you have a custom build process that propogates your code from CVS to target TS environment?

Yes, we do a a process that does this for us. There are a separate groups of techs that maintain this application, however OpenDeploy is at the heart of it.

JAR Reference.zip

vpatel

Ok in that case, I've seen a few customers do this:
1. Anything that is environment specific is tokenized.
2. As part of the build process, those tokens get replaced with the correct value -- this could be done from a custom properties or configuration file.

Would something like that work for your use case?

nipper

We are considering doing processing on the file, but it becomes a pain in the but because we use CVS as our sc repository. We would have to process the file after checkout to make it work in Windows, then process it again before we check it back into CVS.

Is there a way to handle this in CVS?

Thanks in advance,
Lucas

That is because you use CVS. I use a branch in TS and push from iwmount to iwhome. Since OD does it, it can massage the code.

Adam Stoller

You could also put the Unix path in the #! line.
As long as you're not trying to execute the Perl script as a CGI on Windows - Windows doesn't care about the #! line that much (it uses ftype and assocs to determine what script engine to run) - and you can always be explicit and do something like: [iw]perl -w -c script-name.ipl to verify syntactic correctness on the Windows box (though this assumes you have the TeamSite modules loaded on your Windows box.

Also - your post isn't clear about whether your Windows box is a TeamSite box or not.

Ottawa_IWOV

You could also put the Unix path in the #! line.
As long as you're not trying to execute the Perl script as a CGI on Windows - Windows doesn't care about the #! line that much (it uses ftype and assocs to determine what script engine to run) - and you can always be explicit and do something like: [iw]perl -w -c script-name.ipl to verify syntactic correctness on the Windows box (though this assumes you have the TeamSite modules loaded on your Windows box.

Also - your post isn't clear about whether your Windows box is a TeamSite box or not.

Thanks for this response Fish!

The Windows box is a TeamSite box (6.7.2).
I find that if I change the #! line on the /iw-bin scripts, then they break. Is there a way around this?

nipper

Thanks for this response Fish!

The Windows box is a TeamSite box (6.7.2).
I find that if I change the #! line on the /iw-bin scripts, then they break. Is there a way around this?

I asume these are CGI ? There is really no way of not changing them.

Ottawa_IWOV

I asume these are CGI ? There is really no way of not changing them.

That's what my initial hunch was telling me. I think we can integrate an ANT script into CVS that could do some of this work for us.

Thanks,
Lucas

nipper

That's what my initial hunch was telling me. I think we can integrate an ANT script into CVS that could do some of this work for us.

Thanks,
Lucas

Which is why I always use TS and OpenDeploy for this case.

The other thing you can do is make the original code a stub and the use

do, require or eval:

Uses the value of EXPR as a filename and executes the contents of the file as a Perl script.

do 'stat.pl';is just like

eval `cat stat.pl`;

from http://perldoc.perl.org/functions/do.html

Note, Ghoti will chastise me because this will be slower than native. But it may not make a huge difference and if this update happens often, it is worth it

Ottawa_IWOV

Which is why I always use TS and OpenDeploy for this case.

The other thing you can do is make the original code a stub and the use

do, require or eval:

Uses the value of EXPR as a filename and executes the contents of the file as a Perl script.

do 'stat.pl';is just like

eval `cat stat.pl`;

from http://perldoc.perl.org/functions/do.html

Note, Ghoti will chastise me because this will be slower than native. But it may not make a huge difference and if this update happens often, it is worth it

Could I trouble you to provide a more specific example with syntax. That would be excellent.

Thanks for taking the time to help me on this ... another reason why DevNet is such a valuable resource.

Thanks,
Lucas

nipper

I actaully have never done it but it looks pretty easy

If I have a chance I wlll write a sample

nipper

Here you are. It was trivial

iwperl stub.ipl
The stub is running
The included perl is running