[p4] encapsulation of third party software

[Weintraub, David]

Heck, if you figure it out -- let us know. I am building a new
CruiseControl server, and now am spending the entire day installing all
the friggin' packages. I hate Windows. I hate Bill Gates for coming up
with Windows. As we say in New Jersey. "If something bad would happened
to Mr. Gates, it would not make my heart unhappy."

What we do is put all the install packages (with instructions) into a
DevTools directory in Perforce, and all users are suppose to install
them into their PCs. If you are not using .NET, all the tools must be
installed in the same directories, so they're the same from machine to
machine. Otherwise, you have to depend upon the PATH variable which is
limited to 1024 characters. If you're using .NET, things are a bit
easier if you only use .NET compatible tools because .NET looks in the
Windows Registry to see where the DLLs actually lie instead of depending
upon the PATH variable.

As I said, the best we can do is some READMEs, and putting all installs
in a DevTools directory for developers to download and install.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Monica Sanchez
Sent: Tuesday, October 03, 2006 2:49 PM
To: perforce-user at perforce.com
Subject: [p4] encapsulation of third party software

Hi,

 

This question is not 100% related to perforce but to the OS. Most of my
experience is with UNIX systems, but I'm working with Windows now and
I'll like to know how you manage the third party software. My main goal
is to identify and manage tools that "maybe" affect the OS directories
for DLLs and libraries files.

 

While I was working on UNIX I had this big application file system,
where most of the applications were installed and all the users run this
application from the same place.

 

Using Windows, most of the tools affect user account, OS directories and
also the registry.

 

My goal is to implement a process where I can come back to previous
releases, just sync the source from perforce and then be able to build
them.

Our build process is now defining system and registry variables, so I'll
have not problems with the path or any other variable.

 

How do you manage these tools for previous releases?

Thanks,

Monica

 

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user