[pacman-dev] Differences between the makepkg/pacman config in pacman's git and the ones in the pacman package

Dan McGee dpmcgee at gmail.com
Mon Jun 13 20:58:41 EDT 2011

On Mon, Jun 13, 2011 at 7:52 PM, Eric Bélanger <snowmaniscool at gmail.com> wrote:
> On Mon, Jun 13, 2011 at 6:13 PM, Dan McGee <dpmcgee at gmail.com> wrote:
>> On Mon, Jun 13, 2011 at 5:03 PM, Eric Bélanger <snowmaniscool at 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
>> 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=0c29eb431a26467fc5ec14742cfcdc7ce3558334
> And it first appeared in pacman 3.4.3.
> Do you want me to send a patch against maint or master, or for both?

maint is best in that case, no need for master.

As an FYI, anything that gets patched on maint will always make it
into master, as all changes there are merged "up" into master. This
one will be a bit funny as I know there will likely be a conflict with
the signing stuff, but I have no problem resolving that when I do the


More information about the pacman-dev mailing list