On 10 Dec 2020, at 6:12 pm -0800, Colin Woodbury wrote: > 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.
If I may propose an alternative, this seems like an ideal use for .../pacman/.git/info/exclude. For those who don't know, .git/info/exclude is a secondary gitignore file not under version control. It is specifically for files that shouldn't be ignored at the project level, but that an individual developer or user might want to ignore--such as for build artifacts in non-standardized places, or your personal wrapper scripts for testing whatever you're working on. Cheers, Ivy
signature.asc
Description: PGP signature
