slowly losing my will to live as i dive deeper into apk-tools + Alpine + /usr merge + ...

npub1466…uy9c

2024-07-09 03:29:38

slowly losing my will to live as i dive deeper into apk-tools + Alpine + /usr merge + pmbootstrap

i mean, it's solvable, the constraints are just so tight. Like... dynamically fixing Alpine packages so they work on a /usr merge system at runtime requires handling every possible case, like all of these symlinks needs to be detected and skipped (since with /usr merge they become recursive):<li>/bin/foo -> /usr/bin/foo</li><li>/bin/foo -> ../usr/bin/foo</li><li>/usr/bin/foo -> /bin/food</li><li>/usr/bin/foo -> ../../bin/foo</li>

then the same for /lib -> /usr/lib and /usr/sbin

Plus, simply making them absolute symlinks is extremely bad behaviour since it breaks operating on a foreign rootfs (apk --root ...), we just ignore this for now...

And then you get caught out by crap like /bin/go being a symlink to /usr/lib/go/bin/go

i think im getting close, but hitting some weird issues with pmb and apk3...

it would probably not be so bad if I didn't also have to write all this in C

https://gitlab.com/postmarketOS/apk-tools/-/commit/954af7ba48c492cca87b333b0be578a9877cce7a

Author Public Key

npub1466cgkdhvnf7knkdcvz2yl33ra7hek405dr3k22ems3xqrknmjgqvfuy9c

Seen on

wss://relay.nostr.band

Show more details

Published at

2024-07-09 03:29:38

Kind type

1 Short Text Note

Event JSON

{ "id": "cd9abab1aff568f0bc86678ff0ae5cfc9239aa4a1d3672ca158b214985139a65", "pubkey": "aeb58459b764d3eb4ecdc304a27e311f7d7cdaafa3471b2959dc22600ed3dc90", "created_at": 1720495778, "kind": 1, "tags": [ [ "proxy", "https://social.treehouse.systems/@cas/112754411327996639", "web" ], [ "proxy", "https://social.treehouse.systems/users/cas/statuses/112754411327996639", "activitypub" ], [ "L", "pink.momostr" ], [ "l", "pink.momostr.activitypub:https://social.treehouse.systems/users/cas/statuses/112754411327996639", "pink.momostr" ], [ "expiration", "1723087786" ] ], "content": "slowly losing my will to live as i dive deeper into apk-tools + Alpine + /usr merge + pmbootstrap \n\ni mean, it's solvable, the constraints are just so tight. Like... dynamically fixing Alpine packages so they work on a /usr merge system at runtime requires handling every possible case, like all of these symlinks needs to be detected and skipped (since with /usr merge they become recursive):\u003cli\u003e/bin/foo -\u0026gt; /usr/bin/foo\u003c/li\u003e\u003cli\u003e/bin/foo -\u0026gt; ../usr/bin/foo\u003c/li\u003e\u003cli\u003e/usr/bin/foo -\u0026gt; /bin/food\u003c/li\u003e\u003cli\u003e/usr/bin/foo -\u0026gt; ../../bin/foo\u003c/li\u003e\n\nthen the same for /lib -\u003e /usr/lib and /usr/sbin\n\nPlus, simply making them absolute symlinks is extremely bad behaviour since it breaks operating on a foreign rootfs (apk --root ...), we just ignore this for now...\n\nAnd then you get caught out by crap like /bin/go being a symlink to /usr/lib/go/bin/go\n\ni think im getting close, but hitting some weird issues with pmb and apk3...\n\nit would probably not be so bad if I didn't also have to write all this in C\n\nhttps://gitlab.com/postmarketOS/apk-tools/-/commit/954af7ba48c492cca87b333b0be578a9877cce7a", "sig": "ef019365146e88ef569b6a360215a863b8a2d814b7b4b790533dc0b5488d6a8a33567510c42399eda14b2fb8b66794e7e7da546f1531a0046271b4044d02fcf0" }