talismanick has quit [Read error: Connection reset by peer]
snakedye has quit [Ping timeout: 248 seconds]
vipulogmx has quit [*.net *.split]
flub has quit [*.net *.split]
romangg has quit [*.net *.split]
bfiedler has quit [*.net *.split]
flub has joined #river
bfiedler has joined #river
romangg has joined #river
vipulogmx has joined #river
talismanick has joined #river
lxsameer has joined #river
elshize[m] has quit [Quit: You have been kicked for being idle]
Guest32 has joined #river
Guest32 has quit [Client Quit]
snakedye has joined #river
talismanick has quit [Ping timeout: 260 seconds]
icp has joined #river
<icp>
Is there any downside of using the github release binary of river instead of waiting for a update from the distribution? Does that risk running into runtime dependency issues?
<ifreund>
icp: there are no binary relases of river on github, just source code tarballs
<ifreund>
if you're tired of waitng for a distro to update river, it's fairly easy to build from source if you have the latest wlroots release available
<ifreund>
you can get a statically linked zig binary from ziglang.org/download
<icp>
oh okay, I thought the fist tar.gz file in release was an bin release file while the last two were source codes
<ifreund>
the last two are autogenerated github things I don't think I can get rid of
<icp>
I was having a couple of issues I didn't wanna make tickets since I don't know if they were 0.1.1 specific or not so I was waiting to catch up versions but it never comes!
<ifreund>
river-0.1.3.tar.gz includes submodule sources, has a stable checksum, and is PGP signed, unlike the autogenerated github crap
snakedye has quit [Ping timeout: 272 seconds]
<ifreund>
icp: I assume you're using void? For whatever reason no void maintainer has had the time/motivation to review/merge any LLVM update PRs
<icp>
Yep, I made some local bin-packages from github releases for things which have been blocked so hoping river would have one too
<ifreund>
I would do one if statically linking mesa was possible... sadly it isn't though
<icp>
ah, didn't know that.
waleee has joined #river
snakedye has joined #river
icp has quit [Quit: Client closed]
gwizon has joined #river
gwizon has quit [Client Quit]
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
<mizzunet>
@dnkl fuzzel cause to crash river when --lines has a value that fuzzel need to show more tthan the display height.
<mizzunet>
That is, ` fuzzel --prompt=" > " --font="JetBrains Mono":size=12:weight=light --width 25 --horizontal-pad=0 --inner-pad=4 --background=212121ff --
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
snakedye has quit [Ping timeout: 248 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
<andrea>
ifreund: I definitely have to fix the version of river-git
<andrea>
The command suggested by the arch wiki returns 0.1.0 as the tag
<ifreund>
andrea: be warned that the version `river -version` currently outputs won't sort lexographically, it should probably be updated to count the commits since the last tag like that arch wiki suggested command
<andrea>
git describe --long
<andrea>
Yeah, but I think that the version should be computed before compilation
<andrea>
I can just copy the logic from the build.zig and fix the commit count
notzmv has joined #river
<ifreund>
andrea: fyi, I just updated river's version generation code to include the commit count since the last tag and comply with the semver spec
<ifreund>
the new format is 0.2.0-dev.74+7c440b8
<andrea>
ifreund: I see you use an hardcoded version
<andrea>
But I have to use git
<andrea>
Why does git describe print 0.1.0 instead of the latest tag?
<ifreund>
0.1.0 is the latest tag
<ifreund>
but 0.2.0 is the version currently in development, which is what I think the version number should indicate
<andrea>
Why not 0.1.3?
<ifreund>
git describe can't possibly know this though, so I have to hardcode it
<ifreund>
andrea: ah, the 0.1.3 tag isn't on master branch
<ifreund>
try running git describe on the 0.1.x branch
<andrea>
In that case I would have to hardcode the branch
<andrea>
Do you know of any git command that would "scan" all branches?
<andrea>
If not I can hardcode the tag directly and change it manually every time
<ifreund>
that would actually be incorrect to do, you're packaging master branch not the 0.1.x branch right?
<ifreund>
there are commits on master not present on 0.1.x
<andrea>
That I did not know
<ifreund>
0.1.x only has bug fixes and a few non-breaking features
<ifreund>
it's also dead at this point and not recieving new backports from master, the next release will be 0.2.0
<andrea>
So you're saying that 0.1.0 is actually the correct tag for master
<andrea>
I don't know if 0.2.0 would be correct
snakedye has quit [Ping timeout: 272 seconds]
<ifreund>
it's the most recent tag on master yes, though I've decided that `river -version` is 0.2.0-dev.whatever until 0.2.0 is released
snakedye has joined #river
<ifreund>
sticking to the arch wiki's recommendation here is not bad, just a bit confusing for users wanting to report bugs.
<andrea>
As always the arch wiki has the answer
<andrea>
"the same as the version published by the author"
<ifreund>
i guess I could put something in the issue template about providing `river -version` output
<andrea>
I can always grep build.zig
talismanick has joined #river
Nulo has quit [Ping timeout: 248 seconds]
talismanick has quit [Read error: Connection reset by peer]