say you have an app that depends on the foo library, with a specific compile time option, on arch that might be libfoo and just have that option on by default, on gentoo it'd be dev-libs/foo[option], on debian, it would need libfoo at runtime and libfoo-devel at build time
you can't *just* make a distro agnostic package manager, flathub *is* a distro onto itself for this very reason, and any "distro agnostic" aur will just be, an arch container
@lanodan@thephd i'll be resuming the cproc patch as well so, yeah
this plus a few other features proposed to c2y (like celeste's `if` declarations) are things i want to implement because i do not want to wait years for them
@julia bugs are bugs be there or not, as a packager, out of all packages i've done, maintained, and as a developer, out of all bugs i've debugged for openrc
only a very small percentage was distro specific, the vast majority of the fixes benefit everyone, not one distro
and where do we draw the line? is a downstream bug if a packager reports a bug that is only hit on some arch you don't run, maybe powerpc or spark? or using some userspace combination you don't personally use?
and if you provide build time options allowing packagers to replace the "report bugs" button to a distro specific bug tracker, they'll happy do it and thus filtering issues further before they get to you
@julia no distribution is asking that though? i don't know where this myth of having to support all distros came from, but that job is the packager's
instead those devs are going around saying that no one else should package anything ever, which is just, not okay, distros exist for a myriad of reasons
@lanodan i don't get why bring up x11 here at all, since i'm pretty sure i've mentioned to @mirabilos before that wlroots supports pixman, so any wlroots based compositor can run fairly well on software, and if any toolkit works on software-only x11, it'll work on software-only wayland with shm buffers
and yes such setup could not run my stupid external-compositing-via-shaders idea, but i doubt such setup can run compositing on x11 well either
@snacks@desea tho what i mostly wanted to say is i don't like the composed variants to have a whole key on the base layout
and as example, i mentioned ptbr, which also uses diacritics on quite a few letters, but i'd equally dislike having a key for ã or é in a ptbr keyboard as well
@snacks@desea looked at it, i’m really not a fan of dedicating keys in the base layer for ä, ü, ö, ß and 3 dead keys, when those can easily be done via the compose key (which i use for ptbr already, ã, õ, é, ç)
otherwise the distribution in the homerow is really similar to dvorak, so i’m considering going with dvorak for “more usable keys on the base layer”
not to mention i can’t use capslock for Mod3 because i already use it for an Esc/Ctrl combo key (esc on tap, ctrl on hold), layer 4 is interesting though
j and k are where c and v is in qwerty, so, close together, not that bad, h is in the same place, and l is a bit more awkward, where p is in qwerty, but i don't often use h/l, but opt to use the mnemonic broader movements like w, b, e, so, it should be fine
a wannabe hacker just going arounda c gremlingif i forget to cw or alt text please scream at me to, thank you♫♪ And yet we laughed despite it all, at this life which has no meaning at all ♪♫