- unroll the base64 encoding main loop
- rename the base64 chunk functions to tail functions
- fixup push_b64_tail to not read beyond end of length
  (now that it is going to be used with raw data instead of
   struct apk_checksum)
- add (un)likely to optimize for sha1/sha256 length blobs

- allows for static, bump or dynamic allocation of the apk_dependencies
- use bump allocator for packages and dependencies
- adjust package reading to clone apk_package on insert to database

these are often shared in subpackages

xattrs are only present when the tar or extraction framework
makes a callback, so clean them up there explicitly.

speeds up things considerably

fixes #10995

This allows removing (and replacing with some other package)
a package providing the given name. Useful to e.g. allow
"apk del wine-staging" to enforce replacing it to "wine" if
"wine" is in other dependencies.

fixes #11015

Compare the correct version numbers so that the concrete
package selection works as inteded.

ref #11015

Unconditionally remove the corresponding .apk-new files within
protected paths.

fixes #10950

apk_notice will print to stderr without prefix. This avoids
printing any unintended output to stdout which could cause
breakage in file formats that some applets output to stdout.

fixes #10993

now users that want a static apk should do something like

 LDFLAGS="-static" meson setup build . -Ddefault_library=static -Dprefer_static=true

Erica Z authored 6 months ago and Timo Teräs committed 6 months ago

these are included from other header files that are already installed.

Sertonix authored 7 months ago and Timo Teräs committed 7 months ago

Also avoids locking when --files has been passed a fifo

Prevent storing false xattrs data for symlinks.

fixes c5d8d286 adb: implement ADB_BLOCK_EXT flavor for large files

Sertonix authored 7 months ago and Timo Teräs committed 7 months ago

ADB_COMP_NONE is special cause we don't allow specifying a
level by having max_level = 0 but we set level to 1 to distinguish
it from default compression.

fixes apk mkpkg --compression none

Sertonix authored 7 months ago and Timo Teräs committed 7 months ago

When the dir passed to --files had xattrs this would cause the fd to be closed too early.

Sertonix authored 8 months ago and Timo Teräs committed 7 months ago

Otherwise constrains in the world file after an error will be ignored and
may cause false package removal.

Fixes #11009

Christian Marangi authored 9 months ago and Timo Teräs committed 9 months ago

There is currently a fundamental problem with how tar are handled
insternally for scriptdb usage.

We totally lack any support and handling for filename in scriptdb that
are longer than 99char. This cause the filename to be cut and have
situation with file ending with:
- kernel-6.6.30~01f651a1bd5c5592d7cf5a98209bdce4-r1.X121290490411c8c2cf47e3
- kernel-6.6.30~01f651a1bd5c5592d7cf5a98209bdce4-r1.X121290490411c8c2cf47e308d95f12d65d011a391.post-instal
- kernel-6.6.30~01f651a1bd5c5592d7cf5a98209bdce4-r1.X121290490411c8c2cf47e308d95f12d65d011a391.post-i
- kernel-6.6.30~01f651a1bd5c5592d7cf5a98209bdce4-r1.X121290490411c8c2cf47e308d95f12d65

This is caused by the fact that POSIX ustar support up to 99char. The
prefix value can only be used to path but can't be used for filename
hence that is not a valuable solution.

To fix this introduce support to apk_tar_write_entry for GNU longnames
extension header. This is already supported by apk_tar_parse but we
couldn't actually add the special header.

With this fix long filename are correctly handled and the cut problem is
solved.

Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>

Christian Marangi authored 9 months ago and Timo Teräs committed 9 months ago

Generalize tar header setup in a dedicated function in preparation for
support of additional header for longnames and PAX extension headers.

Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>