I'd like to warn everybody who is installing the SVN version of CodeLite.
Here my sad history:
I have access to a directory, say /courses/CPP, on a file server of a students' computer lab.
I've installed SVN-CodeLite yesterday with
./configure --prefix=/courses/CPP --plugins-dir=/courses/CPP
make
make -n install (checking it)
make install
Everythings went well (as expected)
Because of missing features due to an old version of wxWidgets, I installed a newer version of wxWidgets
today.
Then again
./configure --prefix=/courses/CPP --plugins-dir=/courses/CPP
make clean
make
make -n install (checking it, but not enough)
make install
now I got the message
uninstalling old version (or similar)
and the whole directory /courses/CPP got nuked.
Fortunately, I lost only a few hours of work, since there is a nightly backup.
But it could have been much worse.
I don't complain since I should have looked more closely to the output of
make -n install
but it's a hard punishment for such a carelessness.
Helmut.
SVN *** EXTREMELY DANGEROUS ***
-
- CodeLite Veteran
- Posts: 98
- Joined: Thu Feb 18, 2010 10:54 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
-
- CodeLite Enthusiast
- Posts: 37
- Joined: Fri Oct 01, 2010 8:32 pm
- Genuine User: Yes
- IDE Question: all
- Contact:
Re: SVN *** EXTREMELY DANGEROUS ***
this happened because of the wrong plugins-dir you entered. there aren't rm -rf lines generated for prefix-pwd but for plugins-dir.. i'm not even sure whether plugins would work if they aren't in the codelite-dir (they are in /usr/lib/codelite by default).
why are you installing it to a non-standard directory anyway?
greets,
nem
why are you installing it to a non-standard directory anyway?
greets,
nem
-
- CodeLite Veteran
- Posts: 98
- Joined: Thu Feb 18, 2010 10:54 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: SVN *** EXTREMELY DANGEROUS ***
I've found the culprit:HJarausch wrote:I'd like to warn everybody who is installing the SVN version of CodeLite.
Here my sad history:
I have access to a directory, say /courses/CPP, on a file server of a students' computer lab.
I've installed SVN-CodeLite yesterday with
./configure --prefix=/courses/CPP --plugins-dir=/courses/CPP
make
make -n install (checking it)
make install
now I got the message
uninstalling old version (or similar)
and the whole directory /courses/CPP got nuked.
Code: Select all
./configure --prefix=/courses/CPP --plugins-dir=/courses/CPP
Now an uninstall is asking for hell.
But
Code: Select all
./configure --prefix=/courses/CPP
This is very irritating,
Helmut.
-
- CodeLite Enthusiast
- Posts: 37
- Joined: Fri Oct 01, 2010 8:32 pm
- Genuine User: Yes
- IDE Question: all
- Contact:
Re: SVN *** EXTREMELY DANGEROUS ***
it's not irritating. maybe my post was a bit unspecific.
if you hand in a custom plugin-dir the default setting gets overridden (thus deleting your custom directory on uninstall). the new makefile (trunk rev) checks for whether plugins-dir is set to /usr/lib and prevents removing it now.
plugins however should be placed in a separate directory like the codelite-directory, for example /usr/lib/codelite, since they get removed completely on uninstall (plugins dir gets deleted recursively) so in your case --plugins-dir=/Course/CPP/lib/codelite would probably have been correct.
it is unnecessary to set this anyway, since the pluginsdir gets auto-set to $prefixdir/lib/codelite (that's why it worked without setting the pluginsdir separately).
so for the record:
prefix (default) = /usr
plugins-dir (default) = $prefix/lib/codelite
and each one gets overriden by the respective userswitch
greets,
nem
if you hand in a custom plugin-dir the default setting gets overridden (thus deleting your custom directory on uninstall). the new makefile (trunk rev) checks for whether plugins-dir is set to /usr/lib and prevents removing it now.
plugins however should be placed in a separate directory like the codelite-directory, for example /usr/lib/codelite, since they get removed completely on uninstall (plugins dir gets deleted recursively) so in your case --plugins-dir=/Course/CPP/lib/codelite would probably have been correct.
it is unnecessary to set this anyway, since the pluginsdir gets auto-set to $prefixdir/lib/codelite (that's why it worked without setting the pluginsdir separately).
so for the record:
prefix (default) = /usr
plugins-dir (default) = $prefix/lib/codelite
and each one gets overriden by the respective userswitch
greets,
nem
-
- CodeLite Veteran
- Posts: 98
- Joined: Thu Feb 18, 2010 10:54 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: SVN *** EXTREMELY DANGEROUS ***
Hi,nemesis wrote:it's not irritating. maybe my post was a bit unspecific.
if you hand in a custom plugin-dir the default setting gets overridden (thus deleting your custom directory on uninstall). the new makefile (trunk rev) checks for whether plugins-dir is set to /usr/lib and prevents removing it now.
plugins however should be placed in a separate directory like the codelite-directory, for example /usr/lib/codelite, since they get removed completely on uninstall (plugins dir gets deleted recursively) so in your case --plugins-dir=/Course/CPP/lib/codelite would probably have been correct.
it is unnecessary to set this anyway, since the pluginsdir gets auto-set to $prefixdir/lib/codelite (that's why it worked without setting the pluginsdir separately).
so for the record:
prefix (default) = /usr
plugins-dir (default) = $prefix/lib/codelite
and each one gets overriden by the respective userswitch
greets,
nem
perhaps the notion "prefix" has trapped me. If I say --prefix=/usr/local I don't expect the package to install something
directly into /usr/local but in some subdirectory.
So, I was expecting CodeLite would install into something like
<PREFIX>/lib/codelite or <PREFIX>/share/codelite
At least, that would cause much less harm if someone misinterprets is like me.
Regards,
Helmut.
-
- CodeLite Plugin
- Posts: 819
- Joined: Wed Sep 03, 2008 7:26 pm
- Contact:
Re: SVN *** EXTREMELY DANGEROUS ***
Hi Helmut,
Just to mention that, in the current svn version, your problem wouldn't have happened. It's now not necessary to specify --plugins-dir at all (though you can if you really want to). If you provide a --prefix, plugins-dir now defaults <prefix>/lib/codelite.
However, I'm not sure how you managed to lose user data, unless you were storing it in the same dir to which you installed CodeLite. I'd suggest that wouldn't be a good place to put it anyway.
Regards,
David
Just to mention that, in the current svn version, your problem wouldn't have happened. It's now not necessary to specify --plugins-dir at all (though you can if you really want to). If you provide a --prefix, plugins-dir now defaults <prefix>/lib/codelite.
However, I'm not sure how you managed to lose user data, unless you were storing it in the same dir to which you installed CodeLite. I'd suggest that wouldn't be a good place to put it anyway.
Regards,
David
-
- CodeLite Expert
- Posts: 120
- Joined: Sun May 10, 2009 6:56 am
- Contact:
Re: SVN *** EXTREMELY DANGEROUS ***
Suggest the title of this thread be renamed: SVN: A warning if using --prefix