[prev in list] [next in list] [prev in thread] [next in thread] 

List:       darcs-devel
Subject:    [darcs-devel] [patch1738] resolve issue1959: no longer require write-access to the	index for read-on
From:       Ben Franksen <bugs () darcs ! net>
Date:       2018-12-10 13:10:28
Message-ID: 1eaf5e1f-09d0-ee42-eb88-a43e4dfeb14e () helmholtz-berlin ! de
[Download RAW message or body]


Ben Franksen <ben.franksen@online.de> added the comment:

> I experimented a bit more and I don't think always using
> removePathForcibly is a good idea, as users might have deliberately
> protected things from being deleted. 

Not sure about that. Do you have an example where that may be useful,
apart from making the whole repo read-only?

> For example
> the issue2271 test expects that "darcs optimize disable-patch-index" 
> will fail to delete the patch index if it's not writable.

If the patch-index is read-only it cannot be updated and will become out
of date. Makes no sense to me.

> I'll do it conditionally only for cases like diff where we are 
> making a private copy of the repository elsewhere.

Fine with me.

__________________________________
Darcs bug tracker <bugs@darcs.net>
<http://bugs.darcs.net/patch1738>
__________________________________
_______________________________________________
darcs-devel mailing list
darcs-devel@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-devel
[prev in list] [next in list] [prev in thread] [next in thread]