On Tue, 5 Mar 2024 at 21:47, Bruno Haible <br...@clisp.org> wrote: > > The programs are also in a libexec/gnubin/ directory, as symlinks, without > the 'g' prefix. See [1] line 80 and [2] line 39. > Indeed.
So, it seems to me that it is simpler to ask the users to put this > libexec/gnubin/ directory in front of their PATH, than to code a workaround > for every program in every GNU package (Gnulib needs GNU 'join' and 'sed' > now, > maybe others later, and there are also other packages). > I'm asking to have a workaround for each program that gnulib uses in one place (in gnulib) rather than have every user of every package who wants to build from git on macOS have to add the PATH workaround, which is the sort of thing I regularly get support requests about. (It was such a user who asked if I could fix my package so they don't have to change PATH to build it, and hence I made the request to gnulib.) My way of dealing with this at the moment without adding the same tips to the documentation of each package is to direct users to my GitHub CI recipe, which needs to contain this information perforce. That way, the workaround is also tested regularly, rather than sitting in e.g. a README file where it will eventually rot. Such info could be added to the Gnulib manual. > I doubt that would help many users (why should they read the gnulib manual just to build software?) but it might help maintainers like me who can in turn pass on the tip to their users. -- https://rrt.sc3d.org
