1. 25 Dec, 2022 1 commit
  2. 22 Dec, 2022 1 commit
  3. 21 Dec, 2022 1 commit
  4. 20 Dec, 2022 2 commits
  5. 24 Feb, 2022 1 commit
    • Timo Teräs's avatar
      solver: do not auto select virtual-only package with one provider · e4dc2373
      Timo Teräs authored
      This reverts most of 0dcbd933 which allowed automatic selection
      of package with a "virtual provides" having only one provider.
      While convenient, it creates problems if multiple versions of the
      same package exist, or if in future other providers would be added
      to one of the repositories. This restore the original behaviour,
      and improve the error message to tell the user to mention one of
      the providers explicitly.
      fixes #10810
  6. 21 Feb, 2022 2 commits
  7. 19 May, 2021 1 commit
    • Timo Teräs's avatar
      solver: don't consider requirer count for preference · 7167bc9e
      Timo Teräs authored
      The original intent was to choose packages to which there is most
      dependencies. However, since the code has evolved this is has been
      mostly obsolete. And in fact now interferes with the provides and
      provides priority mechanism. Remove this as obsolete.
      Fixes #10742
  8. 09 Oct, 2020 2 commits
  9. 24 Aug, 2020 2 commits
  10. 19 May, 2020 1 commit
    • Timo Teräs's avatar
      make the atom functions not use global state · d0edeec8
      Timo Teräs authored
      This greatly helps with memory management on applications that
      may want to daemonize and open/close database several times.
      Also the lifetime and "owner" of memory for all data is now
      explicitly bound to owning struct apk_database, which might
      be helpful when writing language bindings. As side effect, the
      interned "atoms" are unique only within what apk_database, so
      comparing packages from different apk_database may not work
      as expected.
      Fixes #10697
  11. 07 May, 2020 1 commit
  12. 12 Dec, 2019 1 commit
  13. 05 Jun, 2019 1 commit
  14. 12 Nov, 2018 3 commits
  15. 14 Jun, 2018 1 commit
  16. 21 Feb, 2018 1 commit
  17. 03 Jan, 2018 1 commit
    • Timo Teräs's avatar
      split --force to several --force-[type] options · 039ff3bd
      Timo Teräs authored
      This unloads --force as several of the things are really not wanted
      together. E.g. --force-refresh is a lot different from --force-broken-world
      and doing --force to get the other might introduce unwanted behaviour.
      --force is still kept for backwards compatibility and it enables
      most things --force was used for.
  18. 12 Dec, 2017 1 commit
    • Timo Teräs's avatar
      solver: fix potential install_if processing failure, fixes #8237 · 8e7fd3e0
      Timo Teräs authored
      In discovery phase, there was logic to not process packages
      multiple times. However, that logic failed to account the package's
      depth and install_if state for the name being processed. This
      caused install_if processing failure in certain topologies of the
      dependency graph. Adds also a test case that should catch this
      issue reliably.
  19. 02 Nov, 2017 5 commits
  20. 27 Oct, 2017 1 commit
    • Timo Teräs's avatar
      solver: consider virtual provides to exclude non-provides transitively · e03716ff
      Timo Teräs authored
      this fixes package selection when a 'real' package exists, but would
      need to be provided by another package with 'virtual provides'.
      In current package database this can happen with postgresql which is
      also provided by postgresql-bdr. Normally postgresql would be satisfied
      by postgresql, but if any package depends on postgresql-bdr and there's
      no versioned dependency on postgresql this will help apk figure out
      that postgresql-bdr should be used.
  21. 27 Apr, 2017 1 commit
  22. 27 Feb, 2017 1 commit
  23. 22 Jul, 2016 1 commit
  24. 10 Dec, 2015 1 commit
  25. 30 Jan, 2015 2 commits
    • Timo Teräs's avatar
      sort world dependencies alphabetically · cab03b69
      Timo Teräs authored
      this makes 'lbu diff' and aaudit diffs nice when a world
      dependency is added or removed. sorting also makes the ordering
      more deterministic as the world targets constraints are always
      applied in the same order. test suite updated accordingly.
    • Timo Teräs's avatar
      remove reverse dependencies first · 0276e227
      Timo Teräs authored
      when removing large sets of packets, the ordering of removal
      was not quaranteed to honor dependencies. this fixes the removal
      order to be in reverse dependency order as far as possible.
  26. 06 Oct, 2014 1 commit
  27. 19 May, 2014 1 commit
  28. 10 Apr, 2014 2 commits