<ehawkvu`>
riteo: this spec will also cover some of the internal workings of kiss (like giving a diagram of when/where the hooks are called, etc) which the website doesn't yet do.
<ehawkvu`>
phoebos: I totally forgot that you had worked on the man pages! I wonder if there is a way to reuse the work that you did on those here as well
<ehawkvu`>
sewn: it doesn't yet cover the proposals, but if this were to have it's own repo in kiss-community, we could make proposals a formal part of the document over there.
angle has joined #kisslinux
<angle>
hey, does anyone have a copy of the kiss chroot they could croc over to me while codeberg is down?
angle has quit [Quit: Client closed]
angle has joined #kisslinux
<sewn>
angle: tell me why the universe decided you install kiss at this particular time
<angle>
lol, I'm snowed in, and the last time I tried to install it, it went horribly.
<sewn>
what does snowed in mean
<angle>
like my house is surrounded by snow, so I can't leave to go anywhere.
<angle>
I cleared out 50GB of storage on my ssd, and I tried to look for my old chroot from when I first tried to install it, but I guess I deleted it.
riteo has quit [Ping timeout: 260 seconds]
riteo has joined #kisslinux
<phoebos>
raph_ael: I'd love to make a kiss release but ideally people finish removing VERSION markers and adding explicit DESTDIR :v (testuser, sewn, ioraff, asimovsh)
<sewn>
I will never understand why these are removed
<ehawkvu`>
sewn: it also is something that can be achieved through other means
<sewn>
what was Dylan's stance at the time?
<ehawkvu`>
Dylan was the one who added
<sewn>
ehawkvu`: yeah but I'm not willing to have one line in a few hundred packages if I can have one in kiss, and removing the version markers well idk
<ehawkvu`>
sewn: I didn't vote for the removal fwiw
<sewn>
I think that it would be a lot easier to bump packages using version markers, but it was removed anyway
<ehawkvu`>
sewn: I agree
<sewn>
all I know is they were removed because 'i need to download it manually'
<sewn>
and destdir because of like one package afaik
<sewn>
I don't follow discussions too much tbh
<ehawkvu`>
I think the logic behind removing DESTDIR was that it hides behavior
<ehawkvu`>
explicit > implicit, even when more verbose
<ehawkvu`>
is essentially the reasoning
<ehawkvu`>
phoebos: would you mind if I made a repo up on codeberg for the spec file?
<sewn>
ehawkvu`: yeah that makes a lot of sense
<sewn>
what about the rest of the environment variables?
<sewn>
for rust, go. imagine setting compiler! must be explicit
<phoebos>
ehawkvu`: I'm not sure I understand what you want to do with it, apart from collating information from across codeberg issues and the source code?
<ehawkvu`>
I think the other env variables should remain since they prevent weird build issues
<ehawkvu`>
phoebos: I'd like to have a reference for the expected behavior - also if we ever decide to fully switch over to a C version, it can describe what symbols are expected in a hypothetical library
<sewn>
hmph
<phoebos>
I feel like defining a libkiss interface is rather optimistic
<phoebos>
but I don't want to dampen your enthusiasm
<sewn>
libkiss? I thought kiss was simple
<sewn>
if it's simple all it needs is a smol cute specification and a simple primary implementation
<phoebos>
$/kiss-community is certainly a collection for the community but this sounds more like a personal project
<angle>
ehawkvu`: Can you explain what the difference is between your rootfs and the one I'm supposed to download here? codeberg.org/kiss-community/repo/releases
<angle>
But I can just use ext4 for my fs and be fine? as long as I put in the correct grub commands and have efibootmgr installed, it'll automatically make the boot efi stuff?
<angle>
thanks phoebos. I'll read before I start this time.
A_Dragon has quit [Killed (Stx (We're slaying Dragons. Blame it on the KindOne))]