#39 sfcbstage & sfcbrepos non-executable

Usability
closed-invalid
Adrian
sfcb (1090)
1
2005-04-11
2005-04-08
Gareth S Bestor
No

the auto-generated script commands sfcbstage and
sfcbrepos , which are generated from sfcbstage.sh.in
and sfcbrepos.sh.in, are created non-executable.

Should we rename them to sfcbstage.sh.pre.in and
sfcbrepos.sh.pre.in, to produce an executable *.sh file
instead along the same lines as getSchema.sh.pre.in?

Discussion

    • priority: 5 --> 1
     
  • Logged In: YES
    user_id=1198711

    The suffix doesn't contribute to the x flag of the files.
    Perhaps there's some confusion as the "colored" ls gives
    *.sh the "executable color" even if they are not really
    executable.
    Back to the original comment: the scripts are executable
    after they have been make install'ed. I don't know whether
    it is crucial to have them executable in any stage of the
    build process.
    If you think so, a chmod +x must be added to the sfcbrepos
    and sfcbstage targets.

     
  • Logged In: YES
    user_id=1215486

    thnx. I think I had an older non-executable copy of the
    files installed in /usr/local/bin/, hence they stayed that
    way. After removing them and reinstalling, the files in
    /usr/local/bin are now indeed executable, as you state.

    I dont think its necessary to make the files in the source
    directory executable too. Clsing defect.

     
    • status: open --> closed-invalid