06:50 <sad_plan> config.h is already made. so configure is ran beforehand. this means that everyone, each and everytime will build a package in the exact same way, with the exact same configurations. which makes it 100% reproducable. the only difference between users would be compiler flags really. except kernel, and maybe compiler. but unless you made some really niche choices with the compiler, it shouldnt

06:50 <sad_plan> matter

07:05 <sad_plan> packaging is more demanding for oasis though. any and all files that are generated throughout the building process normally, would also need to be included. if you peak inside the package dirs, youd find config.h in more or less all of them. some contains lots of other files aswell. binutils is a good example. on kiss, building binutils is pretty straight forward id argue. less so on oasis

13:55 <icebarf> bruh pico.sh bouncer smoking

13:55 <icebarf> so bad

13:55 <icebarf> it doesn't load all the messages

14:07 <sad_plan> icebarf: time for a new bouncer perhaps? or maybe get your own server instead?

14:09 <aesdef> Dylan is doing somethin on github

14:29 <sad_plan> icebarf: are you sure? i couldnt spot anything missing at first glance anyway

14:31 <sad_plan> aesdef: it appears youre right

14:31 <aesdef> :)

14:31 <dilyn> he archived everything

14:31 <dilyn> :salute:

14:32 <sad_plan> that he did

14:32 <sad_plan> why salute?

14:32 <dilyn> respec

14:33 <sad_plan> wym

14:35 <dilyn> his readme says he's gonna be a farmer

14:35 <dilyn> the king has left the building

14:42 <sad_plan> i noticed. but you wrote respec, without a t

14:51 <phoebos> He's also put the website up on https://kisslinux.github.io

14:51 <phoebos> Does anyone know if github will keep that up despite the repo being archived?

14:52 <sad_plan> wouldnt that take effect immidiatly if it didnt?

14:56 <phoebos> https://stackoverflow.com/questions/68110301/if-you-archive-a-github-pages-repo-will-the-content-at-github-io-persist

14:56 <phoebos> looks like it will stay

14:56 <phoebos> we can rewrite links to point there

14:58 <sad_plan> cool

14:59 <dilyn> I was being cute :v

16:06 <riteo> holy moly, dylan chose the farmer ending

16:06 <riteo> absolute respect

16:08 <riteo> on a funnier note, I like how the cowsay on the website has been "whatsoever a man soweth, that shall he also reap." for years

16:09 <riteo> a bit prophetic

16:10 <dilyn> like this was always the end game or something

16:12 <riteo> I swear, a weight got off my chest or something, knowing that he's well and that he wrapped everything up. The website takeover felt a bit grim.

16:17 <riteo> I'm really happy!

16:17 <riteo> ok now I'll go calm down a bit or something and come back talking still about the oasis build system, if you'll excuse me

16:54 <phoebos> :D

19:34 <aesdef> Lol, Dylan chose the farmer beginning I'd say - he still young

19:35 <aesdef> I'm agreed with you all. Good on him. I hope he comes around once in a while and shares some stories or something about how it's all going. He used to write a lot and is not a bad writer.

21:44 <riteo> aesdef: oh indeed, I didn't mean it to be an absolute ending

21:45 <riteo> it was just a bit of funny pseudo-gaming language

21:50 <angle> our cincinnatus

22:44 <riteo> Okay I'm back. sad_plan: wrt. oasis' build system, that's really interesting!

22:45 <riteo> Yeah it probably makes the package a lot more reproducible but that obviously also limits a lot the environment

22:45 <riteo> that's probably the biggest difference with kiss, which is supposed to be more of a "survival kit" more than a ready-to-use distro, if you get what I mean

22:46 <riteo> I really want to have more consistent packages though. One of my ideas was to use "file dependencies" (e.g. /bin/cc), store an hash or something in the manifest, and use that as a way of seeing if the pacakge changed

22:47 <riteo> (i.e. needed rebuilding. consider that my whole package manager concept relied on minimizing rebuilds through high consistency)

22:48 <riteo> (I'll stop here, no worries) I swear, one day I should distill all of my ideas into a neater document (in english) and share it with y'all. Perhaps you can take some of those ideas and put them in kiss, or perhaps just give me some feedback

23:29 <sad_plan> riteo: yeah, I really do like oasis' buildsystem. its really neat. although for large projects like gcc, or firefox, as examples, im not sure how usable it is.. for that, one can use kiss instead.

23:29 <sad_plan> put all those ideas of yours down, and get to work. youll figure things out as you go