This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: File permissions in GCC-3.3.3 second prerelease
Ian Lance Taylor <ian@wasabisystems.com> writes:
| Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
|
| > | > | The seven files in question are
| > | > |
| > | > | -rwxr-xr-- gcc/config.guess
| > | > | -rwxr-xr-- gcc/configure
| > | > | -rwxr-xr-- gcc/fixproto
| > | > | -rwxr-xr-- gcc/move-if-change
| > | > | -rwxr-xr-- gcc/scan-types.sh
| > | > | -rwxr-xr-- gcc/sort-protos
| > | > | -rwxr-xr-- gcc/config/m88k/m88k-move.sh
| > | > |
| > | > | I had an idea that a well-timed umask in the gcc_release script might
| > | > | be relevant here, but perhaps just chmodding these few files,v on the
| > | > | CVS server would be sufficient.
| > | >
| > | > Thanks for the report. Any CVS expert around to comment?
| > |
| > | John is correct that if we want to chmod o+x these files, the easy way
| > | to do it is directly on the CVS server. CVS doesn't properly version
| > | control the file mode.
| > |
| > | I'll do the chmod if some maintainer wants me to.
| >
| > Please :-)
|
| Done.
Thanks!
| The file modes will now be fixed in new checkouts, and (I think) when
| they are changed and you run cvs update. They won't otherwise be
| changed in working directories--CVS won't recognize the file mode
| change.
Yes, this is one of the advantages of having the release script
checking out from the main repository :-)
-- Gaby