1. 14 Jun, 2018 2 commits
  2. 09 Jan, 2018 1 commit
  3. 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.
      039ff3bd
  4. 28 Nov, 2017 1 commit
  5. 23 Jun, 2017 1 commit
  6. 25 Apr, 2017 3 commits
  7. 27 Feb, 2017 1 commit
  8. 16 Feb, 2016 2 commits
  9. 09 Nov, 2015 1 commit
    • Timo Teräs's avatar
      io, database: preserve [am]time for cached and fetched files · cce4cff5
      Timo Teräs authored
      preserve [am]time for all packages and indexes. this fixes the caching
      error that 'apk update' is after new index is generated, but before
      the used mirror is synchronized. this caused local apkindex timestamp
      to be newer than file in mirror, when in fact it was outdated index.
      
      this also fixes fetched files to have build timestamp so that files
      going to .iso or custom images have proper timestamps (rsync with
      appropriate --modify-window now works)
      cce4cff5
  10. 10 Mar, 2015 2 commits
  11. 08 Dec, 2014 1 commit
  12. 08 Oct, 2014 1 commit
  13. 03 Feb, 2014 2 commits
  14. 06 Jan, 2014 1 commit
  15. 10 Dec, 2013 1 commit
  16. 28 Jun, 2013 1 commit
  17. 19 Jun, 2013 3 commits
    • Timo Teräs's avatar
      81152df2
    • Timo Teräs's avatar
      fetch, del: perform wildcard matching · 9c54ef72
      Timo Teräs authored
      ref #511
      9c54ef72
    • Natanael Copa's avatar
      print: move progress bar update logic to apk_print_progress · adc5b0b1
      Natanael Copa authored
      - let the apk_print functions deal with the forced print itself. We
        avoid that the callbacks need to deal with the force flag. We can
        also get rid of the APK_PRINT_PROGRESS_* defines.
      
      - let the reader of --progress-fd decide how often things are updated
        rather than having a fixed granularity off 1/100 (percent)
      
      - avoid detect screen size and percent/bar calculations in case the
        --no-progress was given
      
      - track satistics for both the ascii bar and percent info and update bar
        only if either percent or bar changes. This makes the bar go smoother
        when width is wider than 100 chars and it makes the percent counter
        go smooth when screen width is less thann 100 chars. It also
        simplifies the callbacks as they no longer need to deal with update
        granularity.
      adc5b0b1
  18. 18 Jun, 2013 1 commit
  19. 17 Jun, 2013 2 commits
  20. 13 Jun, 2013 1 commit
  21. 29 Feb, 2012 1 commit
    • Timo Teräs's avatar
      solver, test: make conflicts unconditional · f27f194d
      Timo Teräs authored
      Solver will now never report partial solution where a conflict
      constraint is not satisfied. The is because with --force we might
      install the partial solution; and if conflicted packages were to
      be installed we might have extra trouble.
      f27f194d
  22. 24 Feb, 2012 1 commit
  23. 16 Sep, 2011 1 commit
  24. 13 Sep, 2011 1 commit
  25. 09 Sep, 2011 1 commit
  26. 07 Apr, 2011 1 commit
  27. 29 Mar, 2011 2 commits
  28. 01 Jan, 2011 1 commit
  29. 11 Jun, 2010 2 commits