On Mon, Jun 13, 2011 at 5:06 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Mon, Jun 13, 2011 at 3:02 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
Hi,
I noticed several differences between the makepkg.conf and pacman.conf in pacman'git compared to the ones that are provided by the pacman package. I realize that some of these changes are Arch specific but some of them seem to be generic enough to be added to pacman' git. Here's a list of these differences. Once there is an agreement on what to change, I could submit a proper git patch.
I have no idea where you got this diff from, is my biggest question.
The differences are minimal; I make sure of this every time I release a new major version. I know of only gz vs xz extension, custom CFLAGS/LDFLAGS, and having pre-configured repositories.
I was using the following diff: diff -Naur ~/arch.git/pacman/etc/makepkg.conf /var/abs/core/pacman/makepkg.conf diff -Naur ~/arch.git/pacman/etc/pacman.conf /var/abs/core/pacman/pacman.conf 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. However, I believe the makepkg.conf man pages still needs to be fix (If you agree, I'll submit a proper git patch) : $ 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