On Mon, May 30, 2005 at 12:10:42AM -0500, John Goerzen wrote: > I might suggest bringing this up on the darcs users mailing list. There > may be others that would have something to say about it. In the > meantime, I believe that the proper thing would be to retitle this bug > "doesn't store permissions" and reassign it to darcs. Does that make > sense to you?
It would be nice to be able to depend solely on darcs to do the right thing and preserve times and permissions. However, darcs-buildpackage's own repositories have them correctly set, they only get lost when calling darcs in dbp-get to make the working directory. So it's possible to retrieve that data even when darcs doesn't do that. At least when the repositories are local. IMHO it might make more sense to leave this bug on this package and open a new one on darcs about losing permissions and access and change times. Something can be done about the former without fixing the later. Of course, fixing the bug in darcs would close this one too. I wouldn't go to using --set-scripts-executable. That's just a kludge. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
