1. 30 Jan, 2016 2 commits
  2. 28 Jan, 2016 4 commits
  3. 27 Jan, 2016 3 commits
  4. 26 Jan, 2016 2 commits
  5. 25 Jan, 2016 3 commits
  6. 17 Jan, 2016 1 commit
  7. 15 Jan, 2016 4 commits
    • Johannes Löthberg's avatar
    • Allan McRae's avatar
      Cast events to void* before passing to callback · 8d9890d3
      Allan McRae authored
      Silence warnings from clang about typecasting alignment.
      Reported-by: Rikard Falkeborn
      Original-patch-by: Olivier Brunel
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
    • Andrew Gregory's avatar
      add alpm_list_append · ab50864a
      Andrew Gregory authored and Allan McRae's avatar Allan McRae committed
      alpm_list_add always returns the provided list making it impossible for
      callers to check whether or not the operation actually succeeded without
      manually comparing the list length before and after.  alpm_list_append
      instead returns a pointer to the newly created list item so that success
      can be checked.
      Signed-off-by: default avatarAndrew Gregory <andrew.gregory.8@gmail.com>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
    • Dominik Fischer's avatar
      test version range restrictions corner case · 9813107c
      Dominik Fischer authored and Allan McRae's avatar Allan McRae committed
      The test introduced herein illustrates a behavior that may be unexpected
      to package writers.
      It creates a package "pkg3" that is configured to depend on a
      "dependency" which version is between 3 and 4, inclusive. Two other
      packages are already present, providing "dependency" in version 2 and 5,
      respectively. So, the situation looks roughly like this:
                       pkg1               pkg3                pkg2
                     provides          depends on           provides
                        |            <------------>            |
      version __________2____________3____________4____________5___________...
      This seems to be enough to satisfy pacman when installing "pkg3". From
      an iterative standpoint, this is completely logical: First, the
      requirement "dependency>=3" is checked. There is a package that
      satisfies this restriction, it is called "pkg2". Afterwards,
      "dependency<=4" is covered in the same way by "pkg1".
      Nonetheless, what a package writer intends when specifying
         depends=('dependency>=3' 'dependency<=4')
      is most probably that pacman should only allow this package to be
      installed when there indeed is a package present that provides a version
      of "dependency" that lies _between_ 3 and 5.
      Signed-off-by: Dominik Fischer <d dot f dot fischer at web dot de>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
  8. 04 Jan, 2016 9 commits
  9. 15 Dec, 2015 9 commits
  10. 09 Dec, 2015 1 commit
  11. 06 Dec, 2015 2 commits