#kisslinux

Unnofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://vid.puffyan.us/H7PvgY65OxA
Earlier messages
<illiliti>probably busybox has no idea about table arg
<testuser[m]>then thats probably out of scope for a KISS specific patch
<illiliti>is upstream interested in busybox compatibility?
<illiliti>but considering how they recklessly harcoded bash and shit, i guess no
<testuser[m]>I meant more like adding the feature to busybox
<testuser[m]>I don't think there's a "portable" alternative to that rule
ella-0_joined
<illiliti>so you want to contribute a patch to busybox? do it then
<illiliti>btw what about toybox
ella-0quit (Read error: Connection reset by peer)
<sad_plan>toybox needs a patch for removing the bash make dep. unless we wanna put bash into the repo..
<sad_plan>its also.. way less complete
<testuser[m]>illiliti: can u read today's conversation about tar and sticky bits
<illiliti>phoebos has sent a fix already and you merged, no?
<phoebos>i'm still unsure about tar -p
<illiliti>or fix depends on tar implementation?
midfavilajoined
<testuser[m]>Its a partial fix
<testuser[m]>sticky bit is preserved, but only as root with busybox tar
<testuser[m]>stick bit is not preserved as regular user with busybox tar
<testuser[m]>but it works in both cases with gtar
<phoebos>^ only with tar -p
seregjoined
<illiliti>i doubt that we can do anything with this bug
<testuser[m]>~~other than C rewrite~~
<midfavila>speaking of bugs and C,
<midfavila>could one you guys take a hot minute to do me a small favor?
<illiliti>not with tar
<illiliti>we could use pax
<midfavila>i need someone to compile XMag with tcc, then attempt to magnify a section of the display and report back any errors
<illiliti>also i doubt that current fix is good fix
<midfavila>there seems to be a problem with tcc potentially generating incorrect output with programs that use Xt inheritance operations... whatever that means
<illiliti>some systems don't support setting sticky bit on files
<illiliti>this could be problematic
<testuser[m]>phoebos: are there more cases that rwx needs to handle other than stick and rwx stuff already present? Eg if you were to do something like this, will it work?
<testuser[m]>https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=flutter#n42
<phoebos>isn't that just adding rw-rw-rw-
<phoebos>rwx handles that already
rohanquit (Ping timeout: 264 seconds)
rohanjoined
<illiliti>imho we should use chroot() rather than inventing our own using KISS_ROOT
<testuser[m]>wdym
<illiliti>i mean chroot() looks cleaner than prepending KISS_ROOT to everything
<illiliti>chroot(KISS_ROOT)
<testuser[m]>You mean in terms of post install files?
<testuser[m]>How else would pkgs get installer
<testuser[m]>if ur talking about KISS
<testuser[m]>not the post* hooks
<testuser[m]>And i think for hooks we should chroot cuz there can be many hooks like for adding users, which won't work without chrot
ioraffjoined
Later messages