GitLab

So you will not get .apk-new files of the new configuration files.

we let bb use /bin and /sbin, all packages overriding busybox must
install the bins in /usr/bin and /usr/sbin

- empty lines comes after not before
- separate pkgname with : when using -v option

apk_hash_delete() actually deletes the file entry, so unlinking
from other lists need to happen before that. Also free the diri
instead of leaking it.

We dont care if a directory have references or not, we care if directory
is relly there.

Only the creator of the direcotry will set the permissions.

This fixes the situation where you install a package owning a dir then
you remove this dir manually and try install a second package also owning
the dir.

For example:

  apk add e2fsprogs-dev
  rm -rf /usr/lib/pkgconfig
  apk add zlib-dev

This reverts commit 600f9e7e.

My bad. This was correct.

This reverts commit 46430ceb.
The problem this was suppoed to fix was fixed by letting apk_db_open()
return with same working dir.

Otherwise creating rootfs from scratch with --initdb cannot be locked
due to the lock file path missing.

Protect files in protected dirs even if the file is not previously
registered in the database. We do so by always extracting to a
.apk-new file name, compare the checksums afterwards and rename if
file was identical.

Add flags field to db open call. Also make error reporting quite a bit
more detailed.

Both variants should work:
 apk --version
 apk <applet> --version

chown will reset the suid bit so we need to set it again.

Otherwise installed db load fails due to internal reasons. This would
cause a lot of other funny stuff happen.