Hi, Maxim Cournoyer <[email protected]> skribis:
>>> 1. 'guix git authenticate' smarter not install its own hooks when >>> working from a Guix checkout (by checking the git remote, for >>> example). > >> I dont think this would be possible for forks as their remote wont >> match the official git repo. And in general, its probably not a good >> idea to use any complicated heuristics for this. A --no-hook option as >> Ludovic suggested would be a good way forward in my opinion. > > How about option 2 then? It'd be a rather simple and effective means to > ensuring > the right hook is in use when working from a Guix checkout. On option 2, I wrote: > That could be quite annoying though, for instance if you do want to > locally modify the hook for some reason and it constantly gets > overwritten. Not convinced! > A '--no-hook' option seems of little value to me at least to fix the > issue at hand, as it would rely on users knowing to use such option it > the first place, and in which context. My idea was that, if we add that ‘--no-hooks’ option, we’d update the “Building from Git” node to mention it. WDYT? Ludo’.
