<riteo>
some people wanted to port it to meson but that PR is in limbo for now
<riteo>
in general I'd call it some very healthy software though, expecially thanks to the community
<riteo>
works on anything, lightweight, hackable, accessible, _very_ great community and all that
<riteo>
i'd add it to community probably if it isn't out of scope after my port is pushed
<riteo>
it'd be the new alpha though
<illiliti>
great community, but with CoC nonsense. sounds sus
<riteo>
nah, they aren't that severe tbh
<riteo>
the guys "at charge" are pretty based and know when and how to joke
<riteo>
no bad words filter nonsense, along with the main branch thing
<illiliti>
i see
<riteo>
(although I agree that it's shorter thus better, but enforcing it because of some sort of social issue sounds dumb)
<riteo>
also the "mods" aren't assholes, even the main developer's contributions goes through all community stuff and really everyone and I mean everyone is on a very leveled field
<riteo>
only once I saw a guy getting kicked IIRC, but they got some problems from what I heard which got exarcebated from the war since they're ucranian
<riteo>
and they got kicked because they argued for everything constantly, i.e. being extremely annoying
<riteo>
and still once they calm down they should be able to come back
<riteo>
so the CoC isn't an issue like you think, they're pretty much just the rules put into a file saying "don't mess with people ok thx"
<illiliti>
i just don't like when CoC contains too much bullshit nonsense. i always feel ... dumb when i read it, like it was written for dumb people(or trolls?) who don't understand how to interact with other people
<illiliti>
also this annoying regulation aspect...
<riteo>
ig it's just formality, luckily it isn't needed much if not at all, at least in the developer chat
<riteo>
I think it's just like those stupid impossible warning in stuff, like "don't give wine to your wii"
<riteo>
so just don't come people saying "but that wasn't in the rules!"
<illiliti>
you're not a punitive system to enforce those dumb rules...
<illiliti>
so it's pointless to have one
<riteo>
dunno, I think that it's kinda useless in the context of godot, but I don't know the darker parts of the community, expecially after the big unity exodus
<riteo>
I don't really mind it and they're really permissive, so who cares. They'll say something similar if you'll ask them probably
<riteo>
although I know that you really don't like them (and in some cases to good reason)
<riteo>
but seriously, these guys won't try to cancel you. Yeah, if you really bother some trans person because you clearly want to go against them they'll note, but they should note it whenever you bother someone IIRC
<riteo>
for any reason, I mean
<illiliti>
i would never attack anyone personally
<riteo>
then you'd be fine
<riteo>
that's literally what the CoC should say IIRC
<illiliti>
yeah
<riteo>
believe me, all rules eventually sound like being written for idiots
<riteo>
because those are the people you want to filter
<riteo>
a group where I stay has very silly rules (although is a bit more severe) and I notice that with time it's getting more uselessly specific expecially because of idiots
<riteo>
at least AFAICT
<riteo>
so yeah, godot's based
<riteo>
I should resurrect the game repo actually, has someone yet?
<illiliti>
nope
<riteo>
I think I will with the merging of the initial port
<illiliti>
fuck, you reminded me that i need to build stalker
<riteo>
what do you mean by build?
<riteo>
i recall a stalker but it's like proprietary
<riteo>
like the second coc said, these texts are meant to people who don't know how to be humans
<riteo>
they're like formal filters to assholes, just so someone can said, it's written there, you knew what you were going into
<riteo>
s/can said/can say/
<illiliti>
> body size
<illiliti>
what else
<riteo>
ergo, not bully someone because of being fat
<riteo>
ergo
<riteo>
don't bother people
<illiliti>
just say don't attack anyone in any way and that's all
<riteo>
again, formality
<illiliti>
you don't need to enumerate this bullshit
<riteo>
i agree thougj
<riteo>
s/thougj/though/
<riteo>
but if we have to there's probably a reason
<illiliti>
formality doesn't work here. you're not a law. you're not a punitive system. judge doesn't work here.
<riteo>
ehhhhh, I recall dumbasses wanting to find loopholes, although it's not a real state law it still makes the banned person know that the mods haven't gone crazy
<riteo>
tbh I'm neutral about this
<riteo>
I agree with your enumeration argument (there might be more loopholes paradoxically) but as long as the community isn't controlled by a bunch of SJWs I don't care
<riteo>
then you just fork. What are they gonna do, cancel you on twitter?
<riteo>
but in the end, who cares lol. Luckily I didn't yet stumble personally on dumb CoCs, which in the end are just the usual rules put into a funny sounding acryonim
<illiliti>
they can enforce trademark law against you xd
<riteo>
what, how
<riteo>
the license's a license
<riteo>
if you really want to be edgy, funny nad trolly you can make a sneed themed fork, forget it and make a serious one
<illiliti>
trademark can overlap license. see firefox(and now rust) case
<riteo>
who cares lol
<riteo>
wait
<riteo>
rust?
<riteo>
seriously?
<riteo>
how can you get angry over the trademark of a programming language?
<riteo>
the literal name and logo of a text only program
<dilyn>
ERROR llvm Filesystem now dirty, manual repair needed.
<dilyn>
kiss will fail to update a package if 1) a file already exists at some path, but 2) that file is supposed to become a directory
<dilyn>
going from llvm 14.0.6 -> 15.0.0
<illiliti>
that's known bug afaik
<dilyn>
I thought so
<riteo>
yeah I stumbled on that too
<riteo>
btw, it's been quite a while dilyn!
<riteo>
I couldn't greet you in time before you disappearing before
<riteo>
how has life been going?
<dilyn>
it has indeed!
<riteo>
crazy
<dilyn>
life has been insane haha. Been learning a lot about launchpad :thinking:
<illiliti>
cursed
<riteo>
do you perhaps work at canonical?
<riteo>
I saw that you did some ubuntu stuff
<riteo>
uh I got reminded of something, what do y'all think about NDAs?
<riteo>
are they avoidable in the work world?
<riteo>
s/work/job/
<illiliti>
nda is ok
<riteo>
I have a really nice opportuinity for a stage as a firmware writer, but oh boy does the idea of an NDA scare me
<dilyn>
NDAs are not avoidable :\
<dilyn>
I do indeed work at canonical!
<riteo>
would NDAs affect my OSS stuff?
<riteo>
dilyn: cool
<dilyn>
in what ways?
<riteo>
dunno, not being able to write it, or possible weird cease and desists
<riteo>
y'know, bad stuff that might put me in trouble for a buncha years
<illiliti>
it's ok, just don't share secret sauce and you'll be fine
<dilyn>
NDAs can only impact you if you've signed one
<dilyn>
^
<riteo>
yeah, but I might sign one
<dilyn>
ask a lawyer :v
<riteo>
Next year I got a chance of doing a stage at writing firmware, the guy was super available, even offering to teach me stuff
<riteo>
but boy those NDAs are really, really scary
<dilyn>
a bit intimidating
<dilyn>
legalese is opaque lol
<riteo>
I want to keep doing stuff, expecially if the stage lasts just like a single summer month
<riteo>
I don't want to die inside for two years
<riteo>
dilyn do you keep writing OSS?
<riteo>
If you say that those are unavoidable perhaps you've signed one (if you can't answer don't worry)
<riteo>
(ignore in case)
<riteo>
dunno, really really scared
<riteo>
BTW, the separate compiler_rt approach is not working
<riteo>
what I mean is that it's a bit sus
<riteo>
it strongly recommends using a monorepo, should I download the whole llvm repo for this or should I just like embed it inside of clang?
<illiliti>
keep doing stuff. don't connect your foss work to real life and stay anonymous if possible. this reduces the chances of being raped at work for violating nda xd
<testuser[m]12>
Hi
Torr has quit [Ping timeout: 272 seconds]
<riteo>
hi testuser[m]12
<riteo>
illiliti: that would mean that I'd have to change nick
<riteo>
my current nick is pretty connected to me
<riteo>
due to historical reasons
<riteo>
I'm kinda fucked
<riteo>
I think I'll wait for the perfect OSS donation powered impossible job or become homeless
<dilyn>
I don't so much write FLOSS, never really have. but my personal time is my own, in general:)
<riteo>
I mean, I don't know whether he would let me sign and NDA for 1 month of stage work in general, I should build the courage to ask
<riteo>
but even then, how much FLOSS work is competitive in regards to cash registers?
<riteo>
dilyn: there's this compiler_rt LLVM project I gotta build somewhere in order to use ASAN
<riteo>
and I thought about making a separate package, but it fusses a lot about wanting the LLVM source tree
<riteo>
at this point I might do the dumbity-dumb thing of building it with clang
<riteo>
I'd love to separate it, but kiss doesn't really allow that
<riteo>
oh, you've enabled it directly in LLVM
<riteo>
along with clang and whatnot
<riteo>
fuck it, I'll just enable it in clang like I wanted to do, I want just to fix my Wayland PR for Godot bruh
<dilyn>
It might be possible to build it standalone but I've never seen it :thinking:
<riteo>
it still sort of depends on LLVM
<dilyn>
ofc
<riteo>
it would've just been nice to split into a separate package, but this isn't Alpine
<riteo>
Uh, I remember another idea I had for my package system, which is also compatible with kiss
<riteo>
dunno if y'all got tired
<illiliti>
tell us
<riteo>
so basically if you want to make a split package on kiss you have to download the same source multiple times
<riteo>
what if the source is simply named after it's checksum and it looks for that?
<riteo>
bam, you can make as many split builds out of monorepos as you want and you're done. While that wouldn't acknowledge single builds to be split it would still be a nice improvement
<illiliti>
good idea
<riteo>
it'd be less navigable through the cache though
<riteo>
but I'm not sure how much that'd impact people, and worst case, just name the folder like the checksum
Torr has joined #kisslinux
Torr has quit [Changing host]
Torr has joined #kisslinux
<riteo>
but meh, dunno how much people care about package source cache
<riteo>
also a dumb text file might be acceptable I think?
<illiliti>
for what?
<riteo>
for describing what's for
<riteo>
if people cared
<illiliti>
i don't think it is necessary
Torr has left #kisslinux [#kisslinux]
<riteo>
yeah you're right
<riteo>
if I really needed it I could simply look into the source file and look for the checksum
<riteo>
a bit tedious but it's not always needed and it might be a pretty big advantage
<riteo>
do y'all think that it's better to pass paths to the stdin or as args?
<illiliti>
depends
<riteo>
because I'm starting to think that perhaps I might make a packager process which takes the files' path
<riteo>
so you build, and send the built file path. What'd be the advandage? More of a silly idea, but which I think can show the way to more useful approaches
<riteo>
What if, and this is silly, I know, a single build could be packaged into multiple sub-packages by sending multiple files to the packager?
<riteo>
what I mean: imagine this huge package which builds once, you send the list of all files, but in the following order: package1 + extra stuff, SEPARATOR or something, package 2 + extra stuff
<riteo>
or something like that, it'd be great in general to avoid adding a tar dependency to the builder now that I think about it
<riteo>
it'd be great because you can make your own package from the CLI
<riteo>
now that I think about it I'm kinda dumb, you don't need the separator! Just run it multiple times
<riteo>
yeah sorry for the idea dump, but I think that perhaps cpio might always have been based
<riteo>
(interface wise)
<illiliti>
and pax, a cpio successor
<riteo>
oh right it got both interfaces
<riteo>
tar and cpio style
<illiliti>
interesting idea riteo
<riteo>
thanks
<riteo>
yeah this modular thing is really opening the door for some interesting and simple applications
<riteo>
I swear as much as I like apk it's really a mess, I recall having issues properly packaging fucking zpaq, I had to manually create folders which I think should've been there
<riteo>
instead of making multiple methods even a single text stream of files would be way simpler
<riteo>
oh thanks y'all for listening to my ideas, talking to someone for some reason really helps
<riteo>
I mean, interesting ideas, but duplicating dependencies inside squashfs images?
<riteo>
that just sounds like static linking with extra steps
<illiliti>
still, some ideas are interesting
<riteo>
yeah, I must admit so
<riteo>
but it's looking for different goals than ours
<riteo>
and also, most of this stuff can be fixed with static linking
<riteo>
regarding the issue with dependency solving and shared libraries being... not shared
<riteo>
althought parallel installations and atomic immutable packages are very interesting ideas, despite maybe having a bunch of weird issues to sort out (which I think he sorta did with excange directories)?