Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

CVS keeps changing file permissions; why does it do that?

changing CVS file permissions
0
10 Posted

CVS keeps changing file permissions; why does it do that?

0
10

In general, CVS doesn’t do a very good job of preserving permissions on files. When you import a project and then check it out, there is no guarantee that the file permissions in the new working copy will be the same as when the project was imported. More likely, the working copy files will be created with the same standard permissions that you normally get on newly created files. However, there is at least one exception. If you want to store executable shell scripts in the project, you can keep them executable in all working copies by making the corresponding repository file executable: floss$ ls -l /usr/local/newrepos/someproj total 6 -r–r–r– 1 jrandom users 630 Aug 17 01:10 README.txt,v -r-xr-xr-x 1 jrandom users 1041 Aug 17 01:10 scrub.pl,v* -r–r–r– 1 jrandom users 750 Aug 17 01:10 hello.c,v Notice that although the file is executable, it is still read-only, as all repository files should be (remember that CVS works by making a temporary copy of the RCS file, doing everything

Related Questions

Thanksgiving questions

*Sadly, we had to bring back ads too. Hopefully more targeted.