1. 03 Jan, 2018 2 commits
    • 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
    • Henrik Riomar's avatar
      add new flag --no-commit-hooks · 23cb1047
      Henrik Riomar authored
      This flag skips running hook scripts
      
      This flag *must* be used during initramfs tmpfs initial install.
      The reason that this new flag is needed is that the hooks will currently
      always fail as musl and /bin/sh is missing at this stage on diskless.
      23cb1047
  2. 02 Jan, 2018 1 commit
  3. 23 Aug, 2017 2 commits
  4. 06 Mar, 2017 1 commit
  5. 27 Feb, 2017 1 commit
  6. 16 Feb, 2017 1 commit
  7. 15 Feb, 2017 1 commit
  8. 22 Jul, 2016 1 commit
  9. 10 Dec, 2015 1 commit
  10. 07 Apr, 2015 1 commit
  11. 07 Oct, 2014 1 commit
    • Timo Teräs's avatar
      db: rework directory permission handling · 09e48d8f
      Timo Teräs authored
      Apk used to reset directory permissions always, but this is undesirable
      if user has modified the permissions - especially during tmpfs boot.
      Though, it is desirable to update the permissions when packaging has
      changed permissions, or a new package is installed and the merged
      permission mask / owner changes.
      
      Thus the new code updates the permissions only if:
       1) We are booting and directory is not in apkovl
       2) The directory is modified by a package install/remove/upgrade
       3) The filesystem directory permission matched database
      
      Additionally "apk fix --directory-permissions" can be used to reset
      all directory permissions to the database defaults.
      
      Fixes #2966
      09e48d8f
  12. 19 May, 2014 1 commit
  13. 05 Aug, 2013 1 commit
  14. 03 Aug, 2013 1 commit
  15. 21 Jun, 2013 1 commit
  16. 20 Jun, 2013 2 commits
  17. 19 Jun, 2013 4 commits
    • Timo Teräs's avatar
      17145f82
    • Timo Teräs's avatar
      all: few behavioural regression fixes · 6da083fc
      Timo Teräs authored
      Wildcard matching with no names should match all packages only for
      info and search applet. "apk del" would otherwise try to delete
      everything, etc.
      
      Fix also interactive mode to ask questions only if we are actually
      changing something.
      6da083fc
    • 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
    • Timo Teräs's avatar
      upgrade: new option: --latest (-l) · d315c901
      Timo Teräs authored
      Select latest version of package (if it is not pinned), and print
      error if it cannot be installed due to other dependencies.
      
      Together with --available, it selects the latest package which is
      present at least in some repository.
      
      This also fixes few solver issues with ordering of package selection
      that got quite apparent with this flag. Namely, we cannot "lock"
      a package until it's reverse dependencies are locked or not all of
      the solver flags are propagated properly.
      d315c901
  18. 18 Jun, 2013 4 commits
  19. 17 Jun, 2013 3 commits
  20. 14 Jun, 2013 1 commit
  21. 13 Jun, 2013 7 commits