[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Testing 1.31
Hi Todd,
The only thing that's installed outside of the library you install
HTTPAPI into (it does not have to be LIBHTTP, that is just the default
name) is a symbolic link in the IFS from /usr/bin/httpapi to the
HTTPQSHR4 program in whatever library you pick.
If you do not use the QShell interface to HTTPAPI, this symbolic link
probably doesn't matter to you at all, in that case, no need to worry
about it. (This is the case for most HTTPAPI users, very few use the
QShell interface.)
If you do use the QShell interface, you probably want to delete that
symlink, and create separate ones in different directories for each
version of HTTPAPI, and have users adjust their PATH accordingly.
Everything else is done in the install library.
-SK
On 2/23/2016 9:04 PM, Todd Settimo wrote:
We are currently on 1.24 and are going to 1.31. We want to test 1.31
against the applications we have using HTTPAPI before we install and,
looking for the easiest route to doing this, our thought is to install
a secondary LIBHTTP lib at 1.31 and layer a project library under it
with the apps in question. It seems pretty basic on the surface. I
guess what we're wanting to know is if there are any objects installed
outside of the LIBHTTP library that are created/affected when a new
installation of the software is installed. Obviously we don't want to
inadvertently step on the existing 1.24 functionality.
Thanks for your time.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------