Basically yes. But upstream said that they don't intend to change it at the moment because of cross platform concern(Windows) and set-scripts-executable is the hack for *nix. It basically works as most things managed by SCM(be it darcs or others) are source code and build scripts so this hack meets 95% of the need(not as good as really store the metadata). I just want it to do the right thing of change all three instead of just the first two(owner/group). This is a bug for set-scripts-executable itself. I have already informed upstream.
--- Isaac Jones <[EMAIL PROTECTED]> wrote: > gary ng <[EMAIL PROTECTED]> writes: > > > testing shell script. It is very simple to > reproduce. > > Just with the following : > > > > mkdir dir1 > > cd dir1 > > echo "#!/bin/sh" > a > > chmod 0755 a > > darcs init > > darcs add * > > darcs record > > cd .. > > darcs get --set-scripts-executable dir1 dir2 > > > > Now dir2/a is 0754, instead of 0755. > > I'm not exactly sure how this feature decides what a > script is. I > assume it uses extensions. I've forwarded this > upstream as a request > to fix the documentation. > > But it sounds like you're actually asking for > general permission > support, which is already filed as a bug: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311156 > > Do you think your bug / feature request is redundant > with that one? > > peace, > > isaac > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
