Right, having `meson` do it automatically would work well. I put forth the patch in the first place because the instructions on the Pacman website (master branch), if followed, place the artifacts in `build/`. Other newcomers to the project like me would hit the same thing, so some automated solution would be nice.
Is there anything we can do to move that `meson` proposal forward, other than complaining loudly? ;) Colin On Thu, 10 Dec 2020, at 17:42, Eli Schwartz wrote: > On 12/9/20 2:14 PM, Colin Woodbury wrote: > > Since it's a transient directory for build artifacts, nothing in there will > > ever > > been committed. Ignoring it also makes IDEs happier during file search. > > > > Signed-off-by: Colin Woodbury <co...@fosskers.ca> > > --- > > .gitignore | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/.gitignore b/.gitignore > > index 01975fd2..638dfe39 100644 > > --- a/.gitignore > > +++ b/.gitignore > > @@ -1,3 +1,4 @@ > > *~ > > *.o > > pacman-*.tar.gz > > +build/* > > I use builddir/ (and upstream usually recommends that these days since > it's less likely to confuse "meson builddir" as a subcommand, compared > to "meson build"). > > This is kind of the problem with trying to ignore a directory that isn't > canonical. > > Instead, I'd prefer to argue upstream in favor of > https://github.com/mesonbuild/meson/issues/6509 > > -- > Eli Schwartz > Bug Wrangler and Trusted User > > > > *Attachments:* > * OpenPGP_signature
