bug#40699: "dist Hook" documentation in manual is incorrect or unclear about write permissions

2020-04-18 Thread Vincent Lefevre
On 2020-04-18 19:11:14 -0400, Nick Bowler wrote: > I guess the note about dist-hooks when packaging from a read-only srcdir > was added because of my bug report[1]. > > I have never noticed read-only _directories_ in the distdir before (I > have assumed they are always created read-write so that

bug#40699: "dist Hook" documentation in manual is incorrect or unclear about write permissions

2020-04-18 Thread Nick Bowler
On 18/04/2020, Vincent Lefevre wrote: > On 2020-04-18 15:04:08 -0600, Karl Berry wrote: [...] >> Also, not that I wrote any of this, but it seems to me that the >> pervasive assumption is that the automake user in fact owns the file >> trees in question. Thus rm -rf should work even if it's mode

bug#40699: "dist Hook" documentation in manual is incorrect or unclear about write permissions

2020-04-18 Thread Vincent Lefevre
On 2020-04-18 15:04:08 -0600, Karl Berry wrote: > Hi Vincent, > > So, if the subdirectories may not be writable, how can the rm in the > first example work without changing the permissions first? > > [namely:] > dist-hook: > rm -rf `find $(distdir)/doc -type d -name

bug#40699: "dist Hook" documentation in manual is incorrect or unclear about write permissions

2020-04-18 Thread Karl Berry
Hi Vincent, So, if the subdirectories may not be writable, how can the rm in the first example work without changing the permissions first? [namely:] dist-hook: rm -rf `find $(distdir)/doc -type d -name .svn` That example belongs to the preceding paragraph

bug#40699: "dist Hook" documentation in manual is incorrect or unclear about write permissions

2020-04-18 Thread Vincent Lefevre
doc/automake.texi contains: @example EXTRA_DIST = doc dist-hook: rm -rf `find $(distdir)/doc -type d -name .svn` @end example @c The caveats described here should be documented in 'disthook.sh'. @noindent Note that