request to have darcs record file executable permissions

See also RT#96 <http://otherbugs.darcs.net//Ticket/Display.html?id=96>.

RT#96 has now been replaced by issue307

Add new patch type: Chmod
Import and merge of RT #106

Philippe Bergheaud <pbergheaud@meiosys.com> 2004-11-30
-------------------------------------------------------
Subject: Add new patch type: Chmod

I wish darcs could to track changes to the permissions of a file (or
directory), primarily the Unix execution bit.


===========================================================================
Timothy Webster <timw@outblaze.com> 2004-11-30
----------------------------------------------

Create an ownership, permission, acl file per filesystem meta-data
finger print
and apply it when such filesystem is detected.
-tim.


===========================================================================
Philippe Bergheaud <pbergheaud@meiosys.com> 2004-11-30
------------------------------------------------------

Thanks.

On Sat, Dec 10, 2005 at 02:56:45PM +0000, Mark Stosberg wrote:
> request to have darcs record file executable permissions

I'm documenting the workarounds I know about here.

1. The most common case is where you want scripts to be executable.
   For this, the --set-scripts-executable heuristic can be used -- it
   will make files in the working tree executable if they begin with a
   shebang.  You can make this behaviour the default by placing

       ALL set-scripts-executable

   in your .darcs/defaults (per-user) or in _darcs/prefs/defaults
   (per-repo).

2. metastore is a third-party tool that provides metadata storage to
   arbitrary VCSs.  Early versions of etckeeper used it (until it was
   replaced by a NIHd clone).

     http://david.hardeman.nu/software.php

   I haven't used it myself, but I imagine it's straightforward to
   integrate using hooks on record and apply.

I think there's a chance we could implement this (albeit in a somewhat hokey
way) if we had issue743 down.

I'd like to vote for this.  Some of my work is in Rails apps, and Rails 
has a "script" folder with executable scripts in.  It's annoying having to 
chmod them by hand.

On Thu, 20 May 2010 14:46:20 +0000
Ashley Moran <bugs@darcs.net> wrote:

> 
> Ashley Moran <ashley.moran@patchspace.co.uk> added the comment:
> 
> I'd like to vote for this.  Some of my work is in Rails apps, and Rails 
> has a "script" folder with executable scripts in.  It's annoying having to 
> chmod them by hand.

Ashley,

Have you considered setting the "--set-scripts-executable" preference
globally in your darcs repo? That would take care of making sure that
scripts receive executable permissions.

   Mark

On May 20, 2010, at 3:55 pm, Mark Stosberg wrote:

> Have you considered setting the "--set-scripts-executable" preference
> globally in your darcs repo? That would take care of making sure that
> scripts receive executable permissions.

Hi Mark

I saw some of the comments, and I might do that.  Not a huge prob for me as I only generally have to do it once for a project.  But it's something I think should be fixed properly.  It doesn't sell Darcs well that it can't do file permissions (I was quite surprised - I take it for granted in other VCSs).

Ashley

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran

This has come up frequently enough that we should consider it a feature 
request more than a wishlist item.

BTS training: see http://wiki.darcs.net/BugTracker/PriorityStatus on the 
(currently very fuzzy!) difference between a feature and a wishlist 
item.