#kisslinux

Unofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://yewtu.be/watch?v=S81bNIK4MaE
Earlier messages
<dilyn>I'm basically using all of extra from repo/
<dilyn>no you can package more-itertools
<dilyn>i just did, now python-yaml builds just fine
<midfavila>i mean yeah you can
<midfavila>you don't *need* need to
<dilyn>the day I use pip is the day you put me down because I'm obviously an imposter
<midfavila>gonna eat ur brain then
<midfavila>absorb your knowledge
<midfavila>or the imposter's
<midfavila>good enough im sure
<dilyn>I cry https://pastebin.ubuntu.com/p/ddqCcDs3ZT/
<riteo>oof yeah LLVM is required for AMDGPU afaik
<dilyn>it is
<dilyn>but I'm using llvm instead of gcc ;)
<dilyn>I guess mesa uses the .pc which I don't have
<riteo>oof
<riteo>packageconfig my hated
<riteo>is packageconfig seriously the best solution we found for dependency discovery
<riteo>like, why is this problem so hard
<midfavila>portability in general is hard
<midfavila>it's why i program to spec and throw everything else in the garbage
<riteo>I mean isn't posix meant to make portability easy
<riteo>it's in the name
<dilyn>i mean how else would you discover the insane bullshit some folx do...
<dilyn>okay, my issue was a pc issue. now I think I'm hitting a muon issue :v
<riteo>uhhh isn't it supposed to be included from somewhere
<riteo>and isn't that somewhere standard
<dilyn>it can be as standard as we want but some people still use lib lib32 lib64 libx32 and libexec
<dilyn>so how do you decide if it's in /usr/lib or /usr/lib/<triplet> or /usr/lib64/<triplet>?
<riteo>I see
<dilyn>and by "some people" I do mean ubuntu :V :V :V
<riteo>lmao
<riteo>is everything still not linked together?
<riteo>like, what's the point?
<dilyn>they didn't usr-merge until recently and when they did they had to put files in / indicating that usr had been merged lmfao
<riteo>why
<dilyn>a billion reasons
<dilyn>you can't break twenty years of practice willy nilly, as it turns out...
<riteo>isn't the whole point of linking everything together to make things as seamless and compatible as possible
<dilyn>jesus I just checked my /usr/sbin and I have so much shit in there...
<riteo>if it still breaks shit at this point people might have as well stuck onto one options
<dilyn>well yes that is certainly the point of it in part
<midfavila>yeah but ldd depends on paths to link things in at runtime
<dilyn>but you try to update 90,000 packages to deal with that
<midfavila>if you just smack everything in a single directory then it won't find its depends
<midfavila>and yeah
<midfavila>economics of scale makes that simple change a massive problem
<riteo>I see
<dilyn>it was a discussion for *years* leading up to it haha
<dilyn>I think you can see it on the debian ml archive...
Later messages