On Fri, 12 Apr 2002 16:07:28 +1000, Keith Owens <[EMAIL PROTECTED]> wrote: >On Fri, 12 Apr 2002 15:58:56 +1000, >Brendan J Simon <[EMAIL PROTECTED]> wrote: >>In kbuild-2.5-release-1.12, some of the script files are checked for the >>correct permissions (see below for scripts/Makefile-2.5 fragment). >> Instead of trying to change the permissions of the source tree (which >>might be owned by another user, eg. aegis), would it be possible to > >Not everybody runs with a separate object directory. An alternative is >not to execute those scripts directly, instead execute them via >$(KBUILD_SHELL) or $(PERL) as required (kernel-doc is Perl, the others >are shell). Then they do not need execute permissions.
I had a go at this but it is messy. The documentation scripts are a mixture of shell, perl and C and finding all places that assume executable scripts and changing them is ugly, especially docproc.c. I am putting this request in the too hard basket for now and retaining the code that sets execute permissions. Since the permission is only changed if the script is not executable, ask the file owner to mark them executable, this only needs to be done once. Then everybody else gets clean code and there are no permission problems. ... When the solution is worse than the original problem, find another solution ... _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
