Menu
I saw this question but it does not help me. I checked in a file without the executable permission and now, every time I branch or checkout, the file is not executable.
Some other files are indeed saved as executable. I'm guessing that it's because they had the executable bit during first check in--at least that's what my testing leads me to believe.
Does anyone know of a better way to modify (or even at least view) the permissions that subversion has for a file or folder?
292
If you need to manage access via svn:// protocol (embedded authorization), all you need to do is to change files in conf folder of your newly created repository: Set up passwd ( repos/conf/passwd ) in order to define a list of users and passwords.
Subversion does not version permissions. There exist 2 wrapper scripts which you can use instead of “svn” for commit, checkout, update, etc., and store permissions in properties. They are: asvn and svn+perms. Last but not least there is a patch which adds the functionality into the svn core.
Use svn propset as follows:
svn propset svn:executable ON executable_file Then perform svn commit.
157
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
