On Mon, Jun 13, 2011 at 6:13 PM, Dan McGee <dpmcgee@gmail.com> wrote:
I just realized that the makepkg.conf and the pacman.conf files in my git directory aren't tracked by git. They were generated a while ago from the makepkg.conf.in and pacman.conf.in when I ran make to build a git pacman. So the config files are OK. Aha- yeah, these are generated from the .in files in those
On Mon, Jun 13, 2011 at 5:03 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote: directories, so if you haven't run make in a long time they will be quite out of date.
However, I believe the makepkg.conf man pages still needs to be fix (If you agree, I'll submit a proper git patch) : This is a good catch- patches definitely welcome here (for maint I think if it is in 3.5.X series? check where that option was introduced).
The check feature was added on 2010-12-30 by commit: http://projects.archlinux.org/pacman.git/commit/?id=0c29eb431a26467fc5ec1474... And it first appeared in pacman 3.4.3. Do you want me to send a patch against maint or master, or for both?
$ diff -Naur doc/makepkg.conf.5.txt doc/makepkg.conf.5.txt.new --- doc/makepkg.conf.5.txt 2011-06-13 15:07:27.000000000 -0400 +++ doc/makepkg.conf.5.txt.new 2011-06-13 17:59:16.000000000 -0400 @@ -70,7 +70,7 @@ This is often used to set the number of jobs used, for example, `-j2`. Other flags that make accepts can also be passed.
-**BUILDENV=(**fakeroot !distcc color !ccache !sign**)**:: +**BUILDENV=(**fakeroot !distcc color !ccache check !sign**)**:: This array contains options that affect the build environment, the defaults are shown here. All options should always be left in the array; to enable or disable an option simply remove or place an ``!'' at the front of the