Re: [Plplot-general] How to remove an old version

[Jerry <lan...@qw...>]

I actually thought I did the right thing when I installed 5.7.2. But  
for a sanity check I just re-did everything from scratch with the  
same results.

I made a new directory at /usr/local/plplot_run_ccmake_from_here and  
cd-ed to it and ran ccmake from there. From ccmake, I specified  
CMAKE_INSTALL_PREFIX to be /usr/local/plplot-5.7.2.

The result was that only three non-directory items (.m files) were  
stored in /usr/local/plplot-5.7.2 and they are in /usr/local/ 
plplot-5.7.2/share/octave/site/m/PLplot.

Also, a whole lot of stuff was stored in /usr/local/ 
plplot_run_ccmake_from_here and another whole lot of stuff was stored  
in subdirectories of /usr/local, and therein lies the problem because  
as you said /usr/local was where I installed 5.5.3 and is also the  
default for some other things that I have installed. (It seems like a  
dumb policy to put everything side by side so I'm wondering why it's  
so popular.)

Here is the configuration info from ccmake that I set up. As you can  
see, I set CMAKE_INSTALL_PREFIX to /usr/local/plplot-5.7.2 but to my  
eyes the next few lines indicate pending trouble.






Summary of CMake build system results for PLplot

Install location variables which can be set by the user:
CMAKE_INSTALL_PREFIX:      /usr/local/plplot-5.7.2
CMAKE_INSTALL_EXEC_PREFIX  /usr/local
CMAKE_INSTALL_BINDIR    /usr/local/bin
CMAKE_INSTALL_DATADIR    /usr/local/share
CMAKE_INSTALL_LIBDIR    /usr/local/lib
CMAKE_INSTALL_INCLUDEDIR   /usr/local/include
CMAKE_INSTALL_INFODIR    /usr/local/share/info
CMAKE_INSTALL_MANDIR    /usr/local/share/man

Derived install location variables:
DATA_DIR     /usr/local/share/plplot5.7.2
LIB_DIR     /usr/local/lib
INCLUDE_DIR  /usr/local/include/plplot
BIN_DIR     /usr/local/bin
TCL_DIR     /usr/local/share/plplot5.7.2/tcl
DRV_DIR     /usr/local/lib/plplot5.7.2/driversd
DOC_DIR     /usr/local/share/doc/plplot
MAN_DIR      /usr/local/share/man
INFO_DIR     /usr/local/share/info

Other important CMake variables:

CMAKE_SYSTEM_NAME:Darwin
UNIX:1
WIN32:
APPLE:1
MSVC:(MSVC_VERSION:)
MINGW:
MSYS:
CYGWIN:
BORLAND:
WATCOM:

SWIG_FOUND:0
PERL_FOUND:YES
X11_FOUND:1

CMAKE_BUILD_TYPE:
CMAKE_C_COMPILER CMAKE_C_FLAGS:/usr/bin/gcc
CMAKE_CXX_COMPILER CMAKE_CXX_FLAGS:/usr/bin/c++
LIB_TAG:d

ENABLE_DYNDRIVERS:ON
DEVICES_LIST: aqt;mem;null;pbm;plmeta;ps;svg;tk;tkwin;xwin
DRIVERS_LIST: aqt;mem;null;pbm;plmeta;ps;svg;tk;tkwin;xwin

Library options:
BUILD_SHARED_LIBS:ONPL_DOUBLE:ON





In fact, things were installed in the /usr/local tree instead of /usr/ 
local/plplot-5.7.2 as I expected. Here are a few indicative lines  
from /usr/local/plplot_run_ccmake_from_here/install_manifest.txt:


/usr/local/include/plplot/plConfig.h
/usr/local/include/plplot/plDevs.h
/usr/local/lib/libplplotd.dylib
/usr/local/lib/libplplotd.9.dylib
/usr/local/lib/libplplotd.9.2.1.dylib
/usr/local/share/plplot5.7.2/cglobe.map
/usr/local/share/plplot5.7.2/globe.map



Jerry


On Mar 7, 2007, at 10:24 AM, Alan W. Irwin wrote:

> On 2007-03-07 03:42-0700 Jerry wrote:
>
>> I just installed 5.7.2 whereas my previous installation was 5.5.3.
>> How do I get rid of the old versions of everything now that they
>> exist in directories alongside the new version? Or should I have
>> uninstalled the the old version before installing the new version? Or
>> should I just ignore the problem?
>
> Hi Jerry:
>
> In general it is not a good idea to mix versions together with the  
> same
> install-tree prefix.  So specify unique install-tree prefixes  
> (using the
> -DCMAKE_INSTALL_PREFIX cmake option) for each different version you  
> want to
> keep.  Without doubt, -DCMAKE_INSTALL_PREFIX is the most important  
> cmake
> option, and you should use it every time you invoke cmake.
>
> Furthermore, suppose you have installed 5.7.2 in the past with the  
> unique
> install-tree prefix /home/jerry/plplot-5.7.2_install.  Now you may not
> recall the exact configuration you had for that install so that old  
> install
> tree might be filled with plplot files that are irrelevant (or  
> which may
> even interfere) with your new 5.7.2 install.  Of course, one way to  
> avoid
> this stale install file problem is to use a separate install tree  
> prefix
>
> (e.g.,
> /home/jerry/plplot-5.7.2_installa
> /home/jerry/plplot-5.7.2_installb
> /home/jerry/plplot-5.7.2_installb
> ...)
>
> for each separate PLplot-5.7.2 configure, build, and install that  
> you do.
> Probably a more practical course when you are rebuilding and  
> reinstalling a
> particular version of PLplot is simply to remove the whole install  
> tree
> (e.g., with the rm -rf command) before each invocation of "make  
> install".
> Such convenient wholesale removal is only possible because you used  
> a unique
> install-tree prefix such as /home/jerry/plplot-5.7.2_install.  (If  
> you had
> used a generic install prefix such as "/usr/local", then normally  
> there
> would be other files from non-PLplot installs that are mixed into  
> that tree
> which you would not want to remove.)
>
> Of course, that still leaves the question of what to do about your  
> current
> bad situation with various PLplot versions mixed together (possibly  
> with
> non-PLplot files) into the same install tree.  If you built and  
> installed
> PLplot-5.5.3 using the old ./configure; make; make install trio of  
> commands,
> then there is also a "make uninstall" command available to you.   
> However, I
> would only use that in an emergency (such as this) since blindly  
> removing
> files without reviewing them is considered to be dangerous. For modern
> PLplot, there is no "make uninstall" command for exactly this reason.
> Instead, there is a manifest of what was installed in  
> install_manifest.txt.
> Once you have looked at that list and are satisfied that removing  
> all those
> files will cause no harm, then you can conveniently go ahead with such
> removal with, e.g.,
>
> rm `cat install_manifest.txt`
>
> Alan
> __________________________