1. 22 Oct, 2016 2 commits
  2. 23 Feb, 2016 1 commit
  3. 04 Jan, 2016 1 commit
  4. 20 Sep, 2015 1 commit
  5. 20 Jul, 2015 1 commit
  6. 03 Mar, 2015 1 commit
  7. 01 Feb, 2015 1 commit
  8. 27 Dec, 2014 1 commit
  9. 24 Dec, 2014 1 commit
  10. 13 Oct, 2014 1 commit
  11. 30 Sep, 2014 3 commits
  12. 03 Aug, 2014 1 commit
  13. 24 Jun, 2014 1 commit
  14. 08 Mar, 2014 1 commit
  15. 04 Mar, 2014 1 commit
  16. 03 Mar, 2014 4 commits
  17. 07 Feb, 2014 1 commit
  18. 04 Feb, 2014 1 commit
  19. 30 Jan, 2014 1 commit
  20. 28 Jan, 2014 1 commit
  21. 15 Jan, 2014 1 commit
  22. 10 Jan, 2014 1 commit
  23. 06 Jan, 2014 2 commits
  24. 19 Dec, 2013 1 commit
  25. 15 Dec, 2013 2 commits
  26. 31 Oct, 2013 3 commits
  27. 15 Oct, 2013 2 commits
  28. 03 Sep, 2013 1 commit
    • Dave Reisner's avatar
      libalpm: introduce a usage level for repos · 106d0fc5
      Dave Reisner authored and Allan McRae's avatar Allan McRae committed
      
      
      This defines a level of interest a user has in a repository. These are
      described by the bitmask flags in the alpm_db_usage_t enum:
      
        ALPM_DB_USAGE_SEARCH: repo is valid for searching
        ALPM_DB_USAGE_INSTALL: repo is valid for installs (e.g. -S pkg)
        ALPM_DB_USAGE_UPGRADE: repo is valid for sysupgrades
        ALPM_DB_USAGE_ALL: all of the above are valid
      
      Explicitly listing the contents of a repo will always be valid, and the
      repo will always be refreshed appropriately on sync operations.
      
      Signed-off-by: default avatarDave Reisner <dreisner@archlinux.org>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      106d0fc5
  29. 09 Mar, 2013 1 commit