some contrib unix.cbp problems

[killerbot]

Although I was used to building Cb on linux with made, I finally tried it out with the cbp project files.
A few contrib plugins are giving me (similar) problems [Code Snippets and Library Finder].
Focusing on Code Snippets :
the post build -> execution of ./update gives me errors (i compared it to the ./update of wxSmith, they seem very alike, and the wxSmith one works).
This is the error message :

Running project post-build steps
./update
/bin/sh: ./update: Permission denied

Even if I comment all lines of the ./update, I still get this error.

[EDIT] : the wxSmith was is reported as "IsExecutable" in the file properties in Suse 10.2, where the CodeSnippet one is not. I put it manually to isexecutable --> problem remains

[Der Meister]

The problem is the 'update' file. In the wxSmith directory it has the executable flag, which is correct. In 'codesnippets' (and probably in the directory of the lib finder, too) it dosn't have this flag, it is just a regular file.
That means: 'chmod +x update' in both directories should fix your problem.

The other thing is: These problems should be fixed in the svn-repository. As I never used the project files (and thus never touched 'update') the access control flags for these files here are the same as after a fresh and clean checkout. That means that somehow the executable flag can be saved in the svn repository and is indeed stored for some of update-scripts. But obviously not for the update-scripts in these two directories. That means that someone with write access to the repository and with the necessary knowledge should be able to fix this

[killerbot]

Strange, although I already made them executable, they lost it again, made them executable again and now it works.
So still to find out, how to update in svn.

[EDIT]
for 1 of the 2 svn commit thinks something has changed, but I don't know how to write the comment for it (yes I don't know vi, and to be honest, what i see from it now makes me angry) :-(  [so I issued svn commit]
[EDIT2] : kdesvn helped me out : so libfinder done  [well I doubt it, in another view, I did the svn update, and it is still not executable, or should a new clean checkout be done ??]

[EDIT3] : will give up for now, pff, other time better luck ;-)

[stahta01]

Try this; I think this should work under windows, not sure under linux

Code

svn propset svn:executable ON src\plugins\contrib\codesnippets\update
svn propset svn:executable ON src\plugins\contrib\lib_finder\update

Edited command it requires the ON word usage under windows.

Tim S

[Game_Ender]

You can also use the make your commands of the form "svn commit -m "My Message here, that didn't require the use of an editor"".  Or you could just change the default editor in your config or environment.  I think SVN either checks a variables in its config file or uses the EDITOR environment variable.

[killerbot]

thanks for all the info, since I don't have svn on my windows install [in windows for the moment], i tried it out with Tortoise svn and I hoped it worked.
This is what I did : right click in explorer ->Tortoise svn->Properties -> Add
In the drop down box (Property name) choose svn:executable, and as Property value I typed in ON.

[Der Meister]

I just ran 'svn update' and now both files have the executable flags. That means it should work now.