Conversation

the gnu fans are rallying around some extra flimsy arguments to try and justify their failed movement huh

Quote Tweet

Apr 15, 2021

> including Android C and C++ code in Android is compiled with Clang and linked with LLD, not GCC and binutils. That includes the Linux kernel. > tar, gzip or man There are multiple widely used non-GNU implementations of all 3 commands. There's no GNU implementation of man...

Replying to

its a Well Known Fact that the BSDs use pkzip since they don't have tar.

spoobers

just bob, don't be scared

Replying to

and

They don't?

just bob, don't be scared

Replying to

and

I'll be it's patched in on openbsd

Replying to

and

libarchive's tar (FreeBSD tar) will happily extract RAR or CAB file: github.com/libarchive/lib In the Linux world, nearly everyone uses dead Info-Zip from 2008/2009. Has a bunch of known vulnerabilities partially patched downstream by distributions: infozip.sourceforge.net Fun.

Replying to

Yep, a number of patches for that one. cvsweb.openbsd.org/cgi-bin/cvsweb Oh, heh, we pledge(2) unzip too.

Replying to

I really despise Info-Zip. It has terrible performance and I spend a lot of time waiting for zip files to be assembled. An APK file is a zip file with a standard manifest and signature format. An APEX file (source.android.com/devices/tech/o) is an APK with an embedded file system image.

Replying to

Android builds a lot of the OS out of apps and it's used as a packaging format beyond apps. It heavily uses the ability to store files in a zip uncompressed combined with page alignment. Bunch of other zips are built too especially for a release build to be signed + distributed.

5:56 PM · Apr 15, 2021Twitter Web App

Replying to

An incremental build might take a couple minutes with half of that spent dealing with zip files. Signing a release build is largely spent dealing with zip files. Zips are used as an intermediate format for packaging the release and tools used to sign it. Also debug symbols...