definitely will be a problem again if i do get back into kiss
<sewn>
lmk how it goes
<vova>
also
<vova>
wasn't zig in the community repo back in the days ?
<vova>
now there's only zig-bin
<vova>
why
...
<midfavila>
sad_plan vova right now i'm just taking the core of my kiss repos and packing them up
<midfavila>
as usual the problem remains with a native build of GCC >:C
<midfavila>
all my searches result in "lol use a distro that has a native gcc that's easier'
<midfavila>
which is distinctly unhelpful
...
<vova>
what about going gnuless
<vova>
llvm based compiler only instead GCC based
<vova>
instead of GCC based *
<midfavila>
honestly i might use cproc+qbe to bootstrap an old gcc and then from there build a new one
<midfavila>
i'm so fuckin done with gcc's shit though i swear
<riteo>
the cproc route sounds super interesting
<sad_plan>
midfavila: that might be the way to go tbh.
<sad_plan>
you may also try stage0 -> mes -> tinycc-bootstrap -> gcc-2.95 -> gcc-4.7 -> any modern gcc.
...
<vova>
also
<vova>
is anyone really interested in rewriting the kiss package manager ? a new one in C or Zig or whatever, with virtual package, restricted packages (prevent accidental deletion of kiss or busybox), sandboxed build (proot)
<vova>
I started to do it, but I hope it'll replace the POSIX shell version of it
vova I'm, slowly, in my free-free-time working on a lil C implementation myself
<vova>
nice, same !
<riteo>
although my very long term plans are to make a sort of fork of the package format itself to allow some niceties and optimize to a very particular usecase
<riteo>
like, I want to make an as-little-bandwidth-as-possible version of kiss, with all the complexity it might entail
<vova>
I think I'd be a good idea to create a new repo on codeberg to discuss about a new kiss package manager, with yes a new format for the files (except build), like adding a maintainer files, why not a provides file, or even join everything inside a single file like butcher (sabotage Linux)
<riteo>
and other niceties like consistent, isolated buil packaging and shit like that
<riteo>
vova: in my opinion, that would be different from kiss
<riteo>
like, kiss linux is extremely limited. That also makes it extremely simple.
<riteo>
some people might be perfectly fine with that. Think about slackware which is even simpler AFAIU
<vova>
I never used Slackware but from what I've read it's a mix of classic Unix with a port system à la *BSD
<riteo>
also wrt provides, I'd argue that there are a lot of kiss-y ways to implement that and not necessarily a provides file